GNU bug report logs - #62892
proposal to extend mark-sexp to go forward and backward on command

Previous Next

Full log

Message #107 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Eshel Yaron <me <at> eshelyaron.com>
To: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of
 text editors" <bug-gnu-emacs <at> gnu.org>
Cc: drew.adams <at> oracle.com, Zachary Kanfer <zkanfer <at> gmail.com>, juri <at> linkov.net,
 ruijie <at> netyu.xyz, Stefan Monnier <monnier <at> iro.umontreal.ca>,
 Eli Zaretskii <eliz <at> gnu.org>, 62892 <at> debbugs.gnu.org
Subject: Re: bug#62892: proposal to extend mark-sexp to go forward and
 backward on command
Date: Sun, 21 May 2023 17:56:54 +0300

One data point that I think is worth taking into consideration:
Currently, `mark-sexp` and `mark-defun` are not consistent with each
other.  This can be seen in the following example:

--8<---------------cut here---------------start------------->8---
(foo)
(bar)
(baz)
--8<---------------cut here---------------end--------------->8---

With point before `(bar)`, doing `C-2 C-M-SPC C-- C-M-SPC` leaves only
`(bar)` selected.  OTOH, doing `C-2 C-M-h C-- C-M-h` leaves all three
expressions selected.

In contrast, the proposed `mark-sexp-forward` and `mark-defun-forward`
are consistent with each other (both behave like `mark-defun` in the
above example).

I'm not sure if that's the preferred behavior, but I do think that
consistently between the different marking commands is a good thing.


-- 
Best,

Eshel

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.