unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Helmut Eller <eller.helmut@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 33033@debbugs.gnu.org
Subject: bug#33033: 27.0.50; [wishlist] Registers for non-file buffers
Date: Thu, 11 Jul 2019 18:15:12 +0200	[thread overview]
Message-ID: <m2bly01ran.fsf@gmail.com> (raw)
In-Reply-To: <87lfx437kc.fsf@mouse.gnus.org> (Lars Ingebrigtsen's message of "Thu, 11 Jul 2019 17:38:27 +0200")

On Thu, Jul 11 2019, Lars Ingebrigtsen wrote:

> Helmut Eller <eller.helmut@gmail.com> writes:
>
>> 1.) It would be nice if the register machinery could also be used for
>> switching to buffers that aren't connected to a file but have
>> more-or-less fixed names like *shell*, *Backtrace*, or *scratch*.
>>
>> E.g. (set-register ?s '(buffer "*scratch*")) could set up things so that
>> C-x r j s would switch to the *scratch* buffer.
>
> Can you use registers today to jump to buffers that are connected to
> files?  I'm wondering why you're singling out non-file buffers here...

Yes, I have (set-register ?e '(file . "~/.emacs")) in .emacs.

> But in general, it seems to me that these keystrokes aren't that much
> more efficient than just C-x b scr RET or something.
>
>> 2.) Similarly, it would be useful to have a way to switch to a buffer
>> based on the buffer's mode.
>>
>> E.g. (set-register ?l '(mode emacs-lisp)) could switch to the last
>> recently used buffer in emacs-lisp mode.
>
> Hm...  I don't quite see the utility here.

Well, you can close this bug.

Helmut





  reply	other threads:[~2019-07-11 16:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-13  8:09 bug#33033: 27.0.50; [wishlist] Registers for non-file buffers Helmut Eller
2019-07-11 15:38 ` Lars Ingebrigtsen
2019-07-11 16:15   ` Helmut Eller [this message]
2019-07-12 15:14     ` Lars Ingebrigtsen
2021-11-30 14:17       ` Lars Ingebrigtsen

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=m2bly01ran.fsf@gmail.com \
    --to=eller.helmut@gmail.com \
    --cc=33033@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    /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).