From: dieter@duenenhof-wilhelm.de (H. Dieter Wilhelm)
To: 4717@debbugs.gnu.org
Subject: bug#4717: 23.1.50; C-M-h in bibtex mode
Date: Wed, 12 Nov 2014 00:53:32 +0100 [thread overview]
Message-ID: <87tx2547lv.fsf@vsl28t2g.ww011> (raw)
In-Reply-To: <m0r5t71fjf.fsf@cam.ac.uk>
Stefan Monnier <monnier@iro.umontreal.ca> writes:
...
> Ideally BibTeX's C-M-h should not be rebound, and instead
> beginning-of-defun-function and end-of-defun-function should be set in
> such as way that mark-defun marks the same text as bibtex-mark-entry.
I did not yet test it good enough but your idea worked out of the box,
beginning/end-of-defun and mark-defun seem to recognise bibtex entries
already properly without further ado! :-)
>> I would like to volunteer and also argue that point 2) i. e. putting
>> point *behind* a marked element(s) and advancing the marking from point
>> is advantageous for large elements (pages, defuns, paragraphs), when the
>> marked elements might span outside of the current window and the marking
>> commands are repeated. In this case the buffer is scrolled
>> automatically with the new boundary and possible additional marking
>> targets become visible.
>
> Of course, C-SPC M-C-e M-C-e M-C-e would work about as well in that
> case ;-)
And one better - in my opinion - C-M-S-e C-M-S-e ... (But the two
methods are only working like C-M-h when point is already at the
beginning of a defun.)
Anyway, I understand now that it might be better to have two ways of
advancing a region: From point with navigation commands *and* from mark
with marking commands like C-M-e or M-}...
Dieter
--
Best wishes
H. Dieter Wilhelm
Darmstadt, Germany
next prev parent reply other threads:[~2014-11-11 23:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 20:56 bug#4717: 23.1.50; C-M-h in bibtex mode Chong Yidong
2009-10-15 23:09 ` Roland Winkler
2009-10-18 17:09 ` Roland Winkler
2009-10-18 20:31 ` Chong Yidong
2009-10-19 3:38 ` Roland Winkler
2009-10-13 15:26 ` Leo
2014-11-04 16:15 ` H. Dieter Wilhelm
2014-11-05 15:37 ` Stefan Monnier
2014-11-11 23:53 ` H. Dieter Wilhelm [this message]
2022-02-07 0:50 ` Lars Ingebrigtsen
2022-03-07 2:53 ` Lars Ingebrigtsen
2022-03-07 8:18 ` Colin Baxter
2022-03-07 17:39 ` 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
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=87tx2547lv.fsf@vsl28t2g.ww011 \
--to=dieter@duenenhof-wilhelm.de \
--cc=4717@debbugs.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.
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).