From: Bastien <bastien@xxx.fr>
Subject: Re: package that writes *Messages* to a file
Date: Thu, 27 Oct 2005 09:20:34 GMT [thread overview]
Message-ID: <874q73uxcn.fsf@bzg.ath.cx> (raw)
In-Reply-To: v9y84fberc.fsf@marauder.physik.uni-ulm.de
Reiner Steib writes:
> On Thu, Oct 27 2005, Bastien wrote:
>
>> (save-window-excursion
>> (switch-to-buffer "*Messages*")
>
> ,----[ <f1> f switch-to-buffer RET ]
> | WARNING: This is NOT the way to work on another buffer temporarily
> | within a Lisp program! Use `set-buffer' instead. That avoids messing with
> | the window-buffer correspondences.
> `----
>
> Bye, Reiner.
... always learning! thx
--
Bastien
next prev parent reply other threads:[~2005-10-27 9:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.12846.1130373106.20277.help-gnu-emacs@gnu.org>
2005-10-27 1:15 ` package that writes *Messages* to a file Bastien
2005-10-27 7:28 ` Reiner Steib
2005-10-27 9:20 ` Bastien [this message]
2005-10-27 0:23 Harry Putnam
2005-10-27 16:16 ` Kevin Rodgers
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874q73uxcn.fsf@bzg.ath.cx \
--to=bastien@xxx.fr \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).