unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Jacobson <jidanni@dman.ddts.net>
Subject: go to next unsaved buffer
Date: 02 Jul 2002 16:11:34 +0800	[thread overview]
Message-ID: <87y9cuzgzt.fsf@jidanni.org> (raw)

Idea: go to next unwritten file (or whatever you call them).

The proposed "go to next unwritten file command", which merely goes
down the buffer list looking for files that are modified but not
written, will come in handy when:

It's 2:42 and the Royal Ball will start in 5 minutes.  Last time this
happened you just hit C-x s y y y y y without actually looking at
what you were saving.  Bad move.

Now with the new proposed command, you don't have to dig those buffers
out of the buffer list, you just run the command, and it's like "next
please".  And yes, if the current buffer is unwritten when the command
is executed, it cycles to the end of the list (bury-buffer) no matter
what... until there are one or none left...

Ah yes, I forgot to dot that i.  Ah yes, I forgot to cross that t.
Yes, no more hurriedly written buffers.  Each one is brought before
your face for final adjustment and approval.

I propose 'em, you implement them.
-- 
http://jidanni.org/ Taiwan(04)25854780

             reply	other threads:[~2002-07-02  8:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-02  8:11 Dan Jacobson [this message]
2002-07-02 10:38 ` go to next unsaved buffer Paul Stoeber
2002-07-03  5:30   ` Dan Jacobson
2002-07-03 12:16     ` Paul Stoeber
2002-07-03 18:57       ` Andreas Schwab
2002-07-04  6:59       ` Dan Jacobson
     [not found]       ` <200207041824.g64IOXw06480@aztec.santafe.edu>
     [not found]         ` <20020704200235.GA8913@xyz>
2002-07-04 21:46           ` more official key bindings for us follow the leader types Dan Jacobson
2002-07-05  8:54             ` Miles Bader
     [not found]           ` <200207052205.g65M5tS08539@aztec.santafe.edu>
2002-07-06  7:37             ` bind me a/k/a leadership in the key binding dept Dan Jacobson
2002-07-06 10:42               ` Miles Bader

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=87y9cuzgzt.fsf@jidanni.org \
    --to=jidanni@dman.ddts.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 public inbox

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

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).