From: Matthias <cimosque@free.fr>
Subject: Re: buffer-list and desktop
Date: 12 Nov 2004 06:05:50 +0100 [thread overview]
Message-ID: <yg7k6srmzbl.fsf@fermat.math.uvsq.fr> (raw)
In-Reply-To: 2vhofgF2m0kl3U1@uni-berlin.de
Kevin Rodgers <ihs_4664@yahoo.com> wrote:
> (...) The real problem I see is that the buffer browsing commands
> (list-buffers and electric-buffer-list) don't take the list of
> buffers as an argument, so you can't write new desktop-save-
> versions of those commands that use the result of this function.
Exactly! May be one should change `list-buffers' so that it accept a
second optional argument, a list of buffers!!
Thank you very much Kevin, David and Jesper.
--
Matthias
prev parent reply other threads:[~2004-11-12 5:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-10 12:13 buffer-list and desktop Matthias
2004-11-10 19:30 ` Kevin Rodgers
2004-11-10 22:06 ` Kevin Rodgers
2004-11-10 22:18 ` David Kastrup
2004-11-10 22:35 ` Jesper Harder
2004-11-10 22:48 ` David Kastrup
2004-11-11 18:14 ` Kevin Rodgers
2004-11-12 5:05 ` Matthias [this message]
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=yg7k6srmzbl.fsf@fermat.math.uvsq.fr \
--to=cimosque@free.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).