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

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Zachary Kanfer <zkanfer <at> gmail.com>,
 Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: ruijie <at> netyu.xyz, 62892 <at> debbugs.gnu.org, drew.adams <at> oracle.com,
 juri <at> linkov.net
Subject: Re: bug#62892: proposal to extend mark-sexp to go forward and
 backward on command
Date: Sun, 21 May 2023 08:58:35 +0300

> From: Zachary Kanfer <zkanfer <at> gmail.com>
> Date: Sun, 21 May 2023 01:46:21 -0400
> Cc: drew.adams <at> oracle.com, ruijie <at> netyu.xyz, monnier <at> iro.umontreal.ca, 
> 	62892 <at> debbugs.gnu.org, juri <at> linkov.net
> 
> I think I've made as good an argument as I'm going to. It basically boils down to:
> 
> * if the keys are bound, it's quicker to call mark-foo-forward and then mark-foo-backward than to call
> mark-foo, then exchange-point-and-mark, then mark-foo again.
> * This behavior is simpler and more predictable: mark-foo-forward always marks forward. mark-foo
> sometimes marks forward and sometimes backwards. The complexity of the various mark-foo
> functions can be seen in how many cases the docstring has. The behavior of the mark-foo-forward,
> mark-foo-backward functions can be gathered from the name, without reading the docstrings.
> 
> I understand we have different opinions, so if this isn't convincing, I'll bow out here. Thanks.

Stefan, WDYT about this?

Previous Next

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