I'm trying to post the following message to one of the gnu.emacs.help
however, when i click on post, it says
«We were unable to post your message
If you believe this is an error, please contact Google Support.»
I tried post the message as a new thread, but still same error. No
luck after clearing cookies and relogin and or restart Safari browser.
I'm suspecting that google is checking the message content and think
it is spam? cause there are lots of spam blogs or spam newsgroup posts
that contains my name “Xah Lee” or my site and site content
“xahlee.org”. If so, what can i do about it? (i have often reported
such spams thru the report button or google blog help page)
The following is the message content.
«I think the existance of the lisp scratch buffer is one of the major
usability problem of emacs that prevents emacs from being widely
adopted by most text editing audience.»
Giorgos Keramidas wrote:
> Hi Xah ,
> For what it's worth, I think I would appreciate an option that makes the
> current behavior of the *scratch* buffer tunable, i.e. by an option like:
> (defvar scratch-buffer-uses-fundamental-mode nil
> "Non-nil makes the *scratch* buffer use `fundamental-mode'.
> Emacs recreates the *scratch* buffer in `lisp-interaction-mode'.
> If you are not really interested to use `lisp-interaction-mode',
> but you would prefer to start all scratch buffers in
> `fundamental-mode', to start editing text instead of typing Lisp
> expressions, set the `scratch-buffer-uses-fundamental-mode'
> variable to a non-nil value.")
by having a New command with Ctrl+n key, it solves this problem with
scratch plus what you want.
• The New command is a standard across Mac, Windows, Unix (Linux). It
is familiar to all software users.
• The Ctrl+n shortcut for New is standard and familiar to all software
• The New commmand (where the corresponding elisp command name might
will be named new-empty-buffer), can supplant completely the
functionality of *scratch* buffer.
• When users want to have a scratch buffer, he can create it by simply
pressing the shortcut, and when he doesn't want it, he can simply
close it with a standard keystroke Ctrl+w.
• Users can have multiple *scratch* buffers easily without the need to
look into emacs doc.
• The “*scratch*” name is not in some technical jargon sense the best
one. “*untitled*” or “untitled” is a better one, and widely used
across some 99% of OSes and applications. The name “*scratch*” is
unnecessarily narrow, as to indicate that the buffer's content is only
for temp purposes, while “untitled” can include the purpose of
scratch, and can be discarded just as “*scratch*”.
• The respawning of “*scratch*” buffer behavior is unusual, almost
unique to emacs among the thousands of application today. Letting user
have control to create and and discard such buffer is better.
• The “*scratch*” buffer is primarily used by elisp programers. Few
professional programers in the IT industry knows about lisp, and only
minor percentage of emacs users actually code emacs lisp.
> > I wrote some detail about it here:
> > http://xahlee.org/emacs/modernization.html
> But I don't like the `personal attack' style that this text uses, and I
> don't really agree with *all* the proposed `modernization' features.
The Modernization of Emacs article at
does not have any “personal attack” writing style. Perhaps you were
thinking my other newsgroup posts elsewhere where this issue is
> I don't really agree with *all* the proposed `modernization'
If you agree to some, please file a bug report, or help spread the
idea. Thanks for discussing this issue with me.
I think your model can complicate the user interface.
A simple New menu command (create-empty-buffer) that creates a new
buffer in some customizable default mode, solves what you wanted and
it gives you extra power.
Emacs does not provide a user level function to create a new buffer.
It has just New, which actually creates a empty file. Most apps's New
command does not work like that. They actually just create a new
buffer, and only when user save it it becomes a file.
Creating a new buffer is actually quite useful. For example, well
known programer Stevey Yegg in his “Effective Emacs” blog list it as a
top 10 tip in emacs productivity. The emacs menu should have a New
command with Ctrl+n that calls create-empty-buffer.
PS as i mentioned in previous message, i did implement the above. In
my draft code,
• create-new-buffer will create a new empty buffer named “untitled”.
(this should be added the menu command under “File‣New” but i haven't
done that yet.)
• create-new-buffer has standard keyboard shortcut Ctrl+n.
• elisp command close-current-buffer will close the current buffer,
and if it is a buffer not associated with a file (such as “untitled”),
it'll ask user to save (unless it has no content)
• close-current-buffer has the standard keyboard shortcut Ctrl+w.
• close-current-buffer should have menu under “File‣Close”, but it is
not currently done. The existing “File‣Close” menu command calls kill-
this-buffer, which has 2 problems. (1) it doesn't have a shortcut. (2)
it doesn't ask users to save a non-file-associated buffer at all.
(this is major problem that leads to losing data; including
“*scratch*” buffer. The fact that emacs users dont seem to notice this
problem is because it doesn't have a keyboard shortcut, so that
actually nobody uses this command. Most use kill-buffer, which is
annoying because it promps even if the file is already saved.)
You can find the code for the above implementation here:
The code is practically usable, since i use it daily for about half a
year now with incremental improvement and bug fixes, but i'm sure it
can use a lot more polishing for public use.
It is GPL'd, so feel free to grab pieces for your own use or submit
one thing leads to another... i'm going to file a bug report (a
suggestion) on the “*scratch*” now.
(for some reason, google groups won't let me post this message... if
it went thru, that's cause i have to change the content to remove my
name Xah Lee or site xahlee .org cause spammers are using it)