unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Alan Mackenzie<none@example.invalid>
Subject: Re: buffers
Date: Sat, 25 Jan 2003 10:23:04 +0000	[thread overview]
Message-ID: <8iot0b.0d.ln@acm.acm> (raw)
In-Reply-To: _emY9.2066$6U3.12590@newsfep4-gui.server.ntli.net

chris.danx <spamoff.danx@ntlworld.com> wrote on Sat, 25 Jan 2003 02:04:24
+0000:
> Hi,

> I found some code to switch between buffers in the google archives of
> this group, but on some emacs it doesn't work as expected or rather it
> does but it goes to "hidden buffers" that don't show up in others.  At
> home (emacs 21.1.1 on mandrake) it works fine, going to/from any
> buffers open in order but at uni (running rh 7.2 - no emacs version
> number sorry) some buffers are selected which contain lots of symbols
> and err, other junk - it's probably not junk but it's incomprehensible
> to me.  I don't know off hand what these buffers are, only that they
> don't show up at home when cycling through the entire buffer list.

> Is there any way to prevent certain buffers from being selected when
> you cycle through buffers?  Are their "hidden buffers" in emacs?

There are buffers in emacs which do contain, er, junk, but their names
all start with a space.  Go to the *scratch* buffer, and execute
(buffer-list) with C-u C-x C-e.  Note the difference between

#<buffer cc-defs.el>             and
#<buffer  *Echo Area 0*>
         ^
         |

> The code is

> ;switch between buffers
> (defalias 'switch-to-next-buffer 'bury-buffer)
> (defun switch-to-previous-buffer ()
>    "Switches to previous buffer"
>    (interactive)
>    (switch-to-buffer (nth (- (length (buffer-list)) 1) (buffer-list)))
> )

> (global-set-key "\C-c\j" 'switch-to-previous-buffer)
> (global-set-key "\C-c\k" 'switch-to-next-buffer)

It might be an idea to reprogram these commands so that internal buffers
are normally filtered out from the buffer list, but with a C-u prefix,
they would be treated as normal buffers.

> Chris

-- 
Alan Mackenzie (Munich, Germany)
Email: aacm@muuc.dee; to decode, wherever there is a repeated letter
(like "aa"), remove half of them (leaving, say, "a").

  reply	other threads:[~2003-01-25 10:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-25  2:04 buffers chris.danx
2003-01-25 10:23 ` Alan Mackenzie [this message]
2003-01-27 11:59 ` buffers Kester Clegg
2003-01-27 12:43   ` buffers John Paul Wallington
2003-01-27 13:07     ` buffers Kester Clegg
2003-01-28  0:53   ` buffers chris.danx
2003-01-28 11:10     ` buffers Stefan Kamphausen
2003-01-28 12:56       ` buffers Kai Großjohann
2003-01-28 13:20         ` buffers Kester Clegg
2003-01-28 17:13           ` buffers Kai Großjohann
2003-01-29  9:02         ` buffers Stefan Kamphausen
2003-01-28 13:26       ` buffers chris.danx

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=8iot0b.0d.ln@acm.acm \
    --to=none@example.invalid \
    /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).