unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
* inconsistent parsing functions in bibtex-mode
@ 2018-05-30 18:46 Roland Winkler
  2018-05-30 19:35 ` Stefan Monnier
  0 siblings, 1 reply; 4+ messages in thread
From: Roland Winkler @ 2018-05-30 18:46 UTC (permalink / raw)
  To: emacs-devel

Unexpectedly I was hit again by an old problem with bibtex-mode:

This mode defines functions bibtex-beginning-of-entry and
bibtex-end-of-entry which are *similar* to beginning-of-defun and
end-of-defun.  However: repeated calls of these functions do not
move point beyond the current BibTeX entry.  So, while it would be
nice in bibtex-mode to bind beginning-of-defun-function and
end-of-defun-function to these bibtex-mode functions, this won't
work at the moment.

Hence my question: how to deal with this?  I guess the options are:

(1) Keep the behavior of these functions the way they are.

(2) Align the behavior of these functions with what other modes do.

I want to check here before possibly investing more time into option
(2).  I doubt that many people use these commands interactively in a
way that changing their behavior would disturb their work flow.  I
expect that (if at all) this may affect people who have somehow
customized bibtex-mode for their needs.  But it's hard to predict
details.



^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2018-08-08  2:33 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-05-30 18:46 inconsistent parsing functions in bibtex-mode Roland Winkler
2018-05-30 19:35 ` Stefan Monnier
2018-08-07 17:57   ` Basil L. Contovounesios
2018-08-08  2:33     ` Roland Winkler

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).