From: Drew Adams <drew.adams@oracle.com>
To: Emanuel Berg <embe8573@student.uu.se>, help-gnu-emacs@gnu.org
Subject: RE: cycling through windows
Date: Fri, 12 Jul 2013 08:51:57 -0700 (PDT) [thread overview]
Message-ID: <b987c357-5e43-45b2-8a92-e160f0515fe1@default> (raw)
In-Reply-To: <87oba8dttu.fsf@VLAN-3434.student.uu.se>
> (global-set-key (kbd "C-j") 'jump-to-register)
>
> (set-register ?a (cons 'file "/sudo::/etc/apt/sources.list"))
> (set-register ?c (cons 'file "~/.irssi/config"))
> (set-register ?C (cons 'file "/sudo::/etc/default/console-setup"))
> (set-register ?e (cons 'file "~/.emacs"))
>
> Before I started with this system, I lost a lot of time typing
> file paths, iterating the buffer list, etc. Now I just (for
> example) [C-j e] to bring up .emacs - and if there is such a
> buffer already, I get to the correct place (where I had point on
> my last visit).
If you want such persistence then instead of loading code to
recreate the registers each time, just use bookmarks.
That's what they're for.
And bookmarks have hooks, so you can add behavior.
And you can define your own bookmark types, to give you any
behavior you want.
next prev parent reply other threads:[~2013-07-12 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.891.1373604148.12400.help-gnu-emacs@gnu.org>
2013-07-12 9:13 ` cycling through windows Emanuel Berg
2013-07-12 15:51 ` Drew Adams [this message]
2013-07-12 4:42 C K Kashyap
2013-07-12 5:55 ` Jambunathan K
2013-07-12 8:09 ` Thorsten Jolitz
2013-07-12 16:17 ` Teemu Likonen
2013-07-14 6:35 ` C K Kashyap
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=b987c357-5e43-45b2-8a92-e160f0515fe1@default \
--to=drew.adams@oracle.com \
--cc=embe8573@student.uu.se \
--cc=help-gnu-emacs@gnu.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.
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).