unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Branham <alex.branham@gmail.com>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 32378@debbugs.gnu.org
Subject: bug#32378: [PATCH] bibtex-next/previous-entry
Date: Tue, 07 Aug 2018 08:07:12 -0500	[thread overview]
Message-ID: <87lg9itjen.fsf@gmail.com> (raw)
In-Reply-To: <87effa7cul.fsf@tcd.ie>


On Tue 07 Aug 2018 at 04:19, Basil L. Contovounesios <contovob@tcd.ie> wrote:

> Are these commands (or could they be made) suitable for use with
> beginning-of-defun-function and end-of-defun-function, as discussed in
> the following messages?
>
> https://lists.gnu.org/archive/html/emacs-devel/2018-05/msg00820.html
> https://lists.gnu.org/archive/html/emacs-devel/2018-05/msg00821.html

Thanks for bringing those to my attention; I don't subscribe to emacs-devel.

We could certainly modify bibtex-beginning-of-entry to take an optional
argument that allows it to move past the current entry if point is
already at the beginning. I wouldn't want to modify the current behavior
because other packages rely on bibtex-beginning/end-of-entry not to move
past the current one (e.g. bibtex-completion.el and org-ref.el). 





      reply	other threads:[~2018-08-07 13:07 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
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 [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=87lg9itjen.fsf@gmail.com \
    --to=alex.branham@gmail.com \
    --cc=32378@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    /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).