all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glauber Alex Dias Prado <smade4@gmail.com>
To: "B. T. Raven" <nihil@nihilo.net>
Cc: help-gnu-emacs@gnu.org
Subject: Re: save-current-buffer
Date: Sun, 19 Oct 2008 05:24:53 -0200	[thread overview]
Message-ID: <864p39gi7u.fsf@gmail.com> (raw)
In-Reply-To: <0oCdnWtUBfnQ8GfVnZ2dnUVZ_tzinZ2d@sysmatrix.net> (B. T. Raven's message of "Sat, 18 Oct 2008 18:12:35 -0500")

save-current-buffer is a special form in `C source code'.
(save-current-buffer &rest body)

Save the current buffer; execute body; restore the current buffer.
Executes body just like `progn'.

strange indeed,dunno why it works this way.

"B. T. Raven" <nihil@nihilo.net> writes:

> Andreas Politz wrote:
>>
>>
>> Is this a bug, or am I missing something ?
>> Eval this in *scratch* buffer and you end up in the *Help* one.
>>
>> (save-current-buffer
>>   (switch-to-buffer "*Help*"))
>>
>>
>> GNU Emacs 22.2.1
>>
>>
>> -ap
>
> That's what you would expect. If you don't have an Emacs generated
> read-only *Help* buffer open then you will create an editable one with
> that name. Why does it seem like a bug? Of course the file *Help*
> can't be saved because the file name is illegal.
>
> Ed




  parent reply	other threads:[~2008-10-19  7:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-18 20:43 save-current-buffer Andreas Politz
2008-10-18 23:12 ` save-current-buffer B. T. Raven
2008-10-19  2:57   ` save-current-buffer Chris F.A. Johnson
2008-10-20  0:37     ` save-current-buffer B. T. Raven
2008-10-19  7:24   ` Glauber Alex Dias Prado [this message]
     [not found]   ` <mailman.1486.1224401134.25473.help-gnu-emacs@gnu.org>
2008-10-19 10:31     ` save-current-buffer Andreas Politz
2008-10-19 15:44 ` save-current-buffer Nikolaj Schumacher
     [not found] ` <mailman.1511.1224431046.25473.help-gnu-emacs@gnu.org>
2008-10-21 11:26   ` save-current-buffer Andreas Politz
2008-10-21 21:21     ` save-current-buffer Nikolaj Schumacher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=864p39gi7u.fsf@gmail.com \
    --to=smade4@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=nihil@nihilo.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.