From: Noam Postavsky <npostavs@gmail.com>
To: Alex Branham <alex.branham@gmail.com>
Cc: 32378@debbugs.gnu.org
Subject: bug#32378: [PATCH] bibtex-next/previous-entry
Date: Mon, 20 Aug 2018 20:47:25 -0400 [thread overview]
Message-ID: <877ekkwnoi.fsf@gmail.com> (raw)
In-Reply-To: <87efesyh81.fsf@gmail.com> (Alex Branham's message of "Mon, 20 Aug 2018 14:23:58 -0500")
Alex Branham <alex.branham@gmail.com> writes:
> On Sun 12 Aug 2018 at 12:41, Noam Postavsky <npostavs@gmail.com> wrote:
>
>> Would it make sense to use [remap forward-paragraph] and [remap
>> backward-paragraph] instead of "\M-\}" and "\M-\{"? (I guess the
>> question is how "paragraph-like" are these movement commands)
>
> Yes, that probably makes sense. Revised patch attached.
> etc/NEWS | 5 +++++
> lisp/textmodes/bibtex.el | 18 ++++++++++++++++++
> ++++
> +** bibtex
> +*** New commands bibtex-next-entry and bibtex-previous-entry
> +They are bound to M-{ and M-} in bibtex-mode-map.
I guess the NEWS entry should be revised as well. I notice you put
"+++" but haven't made any manual updates, did you mean "---" instead
(i.e., no manual updates are required)?
> + (define-key km [remap forward-paragraph] 'bibtex-next-entry)
> + (define-key km [remap backward-paragraph] 'bibtex-previous-entry)
next prev parent reply other threads:[~2018-08-21 0:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 21:03 bug#32378: [PATCH] bibtex-next/previous-entry Alex Branham
2018-08-07 2:15 ` Noam Postavsky
2018-08-07 13:03 ` Alex Branham
2018-08-12 17:41 ` Noam Postavsky
2018-08-20 19:23 ` Alex Branham
2018-08-21 0:47 ` Noam Postavsky [this message]
2018-08-21 15:19 ` Alex Branham
2018-08-21 15:21 ` Alex Branham
2018-08-27 23:56 ` Noam Postavsky
2018-08-21 2:28 ` Eli Zaretskii
2018-08-21 15:23 ` Alex Branham
2018-08-21 16:09 ` Eli Zaretskii
2018-08-07 9:19 ` Basil L. Contovounesios
2018-08-07 13:07 ` Alex Branham
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=877ekkwnoi.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=32378@debbugs.gnu.org \
--cc=alex.branham@gmail.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.
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).