From: Yevgeniy Makarov <emakarov@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Moving by entries and paragraphs in BibTeX mode
Date: Wed, 16 Jan 2008 10:16:06 -0800 (PST) [thread overview]
Message-ID: <6709ade5-a7f4-41bb-8f85-1b34cf4e3bc6@s12g2000prg.googlegroups.com> (raw)
In-Reply-To: m3abn6s9sd.fsf@tfkp07.physik.uni-erlangen.de
> In BibTeX files, a `paragraph' is used in other context, too. Say
> the function fill-paragraph operates on one field, not on one entry,
> and I find that meaningful.
You are right: this makes sense.
> However, if you jump from one @ to the next / previous @ you are
> most likely jumping from one entry to the other. I guess that typing
> C-s @ is as efficient as executing a command that does perform this
> action.
Thanks, that's a great idea.
prev parent reply other threads:[~2008-01-16 18:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 22:52 Moving by entries and paragraphs in BibTeX mode Yevgeniy Makarov
2008-01-16 3:56 ` Roland Winkler
2008-01-16 18:16 ` Yevgeniy Makarov [this message]
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=6709ade5-a7f4-41bb-8f85-1b34cf4e3bc6@s12g2000prg.googlegroups.com \
--to=emakarov@gmail.com \
--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).