unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: Buffer Navigation
Date: Tue, 18 Oct 2005 20:35:16 -0700	[thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICIEJJCNAA.drew.adams@oracle.com> (raw)
In-Reply-To: <1129690887.411887.235150@g43g2000cwa.googlegroups.com>

    from that wiki entry i found the bs calls... silly me for trying to
    re-implement their simple next/previous stuff. bs-show is nice too.

    however, none of these numerous adons do what i want... which is to
    only navigate through files which i, myself, not some mode or function
    call, have opened. i don't want to go writing out regexs for the types
    of files i usually edit... i just want emacs to be smart enough to know
    what i have opened by hand. is that kind of information stored anyway?
    or is writing a wrapper for open/close the only solution...

Buffer and file commands normally filter out uninteresting buffers (those
whose names start with a space) and files (those whose names match
`completion-ignored-extensions', for example), but that isn't exactly what
you're asking for.

You can certainly write something yourself - just keep track of the buffers
and files you open yourself. If you put their names on a list, you can use
Icicles cycling and completion to access them. But this requires a little
Emacs Lisp.

If a list of recently used files is sufficient for you (they might not still
be open, so this is not exactly what you asked for), then there are
libraries that do that too.

Icicles, for instance, has commands `icicle-recent-file' and
`icicle-recent-file-other-window', which let you open a recently visited
file (filename completion and cycling available, as usual). This uses
library `recentf.el', which persistently records your visited files.

You can also cycle through the files you opened during the current session
only, by using Icicles command `icicle-history' (bound to `M-h' in the
minibuffer). You can use this on any minibuffer input, including filename
input. During file-name completion, it lets you complete to, or cycle
through, your recently visited files of the current session. For instance,
`C-x f', then `M-h', then use up/down arrows to cycle through recent files
and choose one (RET).

(If you use library `savehistory.el', then `icicle-history' uses the
persistent minibuffer histories saved by that library.)

HTH.

  reply	other threads:[~2005-10-19  3:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-19  2:18 Buffer Navigation Shug Boabby
2005-10-19  2:28 ` Drew Adams
     [not found] ` <mailman.11819.1129688923.20277.help-gnu-emacs@gnu.org>
2005-10-19  2:38   ` Shug Boabby
2005-10-19  3:35     ` Drew Adams
2005-10-19  3:01   ` Shug Boabby
2005-10-19  3:35     ` Drew Adams [this message]
2005-10-19 22:54     ` Thien-Thi Nguyen
2005-10-20 22:43       ` Shug Boabby
2005-10-21 17:01         ` Kevin Rodgers
     [not found]         ` <mailman.12151.1129914597.20277.help-gnu-emacs@gnu.org>
2005-10-23 19:54           ` Shug Boabby

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=DNEMKBNJBGPAOPIJOOICIEJJCNAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.com \
    /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).