all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Roland Winkler <winkler@gnu.org>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 56636@debbugs.gnu.org
Subject: bug#56636: 28.1.90; bibtex-beginning-of-entry does not always move point the the actual beginning
Date: Sat, 23 Jul 2022 21:37:05 -0500	[thread overview]
Message-ID: <87wnc36xta.fsf@gnu.org> (raw)
In-Reply-To: <87edycuucy.fsf@localhost> (Ihor Radchenko's message of "Sat, 23 Jul 2022 16:05:33 +0800")

On Sat, Jul 23 2022, Ihor Radchenko wrote:
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>>> Observed: Point moves to the @ ~/.emacs.d line.
>>> Expected: Point moves to @misc
>>
>> I guess the problem is with the @ in the title entry?
>
> Yes, bibtex-beginning-of-entry is doing
> (re-search-backward "^[ \t]*@" nil 'move) which does not match the right
> thing in this particular case.

This old part of the code should use bibtex-entry-maybe-empty-head.

Looking at the code, it frequently performs a strange dance
where a call of bibtex-beginnig-of-entry is followed by
(looking-at bibtex-entry-maybe-empty-head).
That doesn't make sense, it works around the above bug instead of
doing it right in the first place.  I'll look for a better solution
for this.





  reply	other threads:[~2022-07-24  2:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19  2:46 bug#56636: 28.1.90; bibtex-beginning-of-entry does not always move point the the actual beginning Ihor Radchenko
2022-07-23  7:56 ` Lars Ingebrigtsen
2022-07-23  8:05   ` Ihor Radchenko
2022-07-24  2:37     ` Roland Winkler [this message]
2022-07-24  9:24       ` Lars Ingebrigtsen
2022-09-25  6:27       ` Ihor Radchenko
2022-11-25  7:43         ` Ihor Radchenko
2022-11-26 12:57           ` Roland Winkler
2022-11-27  0:08             ` Ihor Radchenko
2022-12-30  5:48               ` Roland Winkler

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wnc36xta.fsf@gnu.org \
    --to=winkler@gnu.org \
    --cc=56636@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=yantar92@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.