Re: Transient Region Highlighting - an improvement over Transient Mark Mode.

["Vincent Belaïche" <vincent.belaiche@gmail.com>]

Dear all,

Sorry to step into a discussion connected to a development I am not 
involved in. Just a few suggestions, hoping that that they can be useful :

1) There are already commands to narrow commands' scope  to the region 
and to widen it to the whole buffer (C-x n n, C-x n w, etc... see *info* 
node Narrowing) , but they are not transient. I think that narrowing 
whether it is permanent or transient (one-shot) should be accessible 
independently from indicating it. So there should be
1.1) three narrowing states = permanent, one-shot, inactive
1.2) a number of command scope narrowing targets (e.g. region, page, 
paragraph, Lisp defun, C-function, sentence, whole buffer) one of which 
is used when the narrowing state is not inactive (ie is permanent or 
one-shot), and that may be accessible depending on buffer mode (e.g. 
Lisp defun has no meaning in text mode)
1.3) one default command scope to be used when the narrowing state is 
inactive (default command scope  should be whole-buffer by default)
1.4) after each command operating on a narrowed portion of buffer, the 
narrowing state should transit as follows:

        +----------+
           V           !
   +----------+       !
   |permanent |----+
   +----------+

   +---------+
   |one-shot |
   +---------+
     !
     !
     !  +----------+
     V     V           !
   +--------+       !
   |inactive|------+
   +--------+


2) Highlighting the region as such is not the relevant thing to the 
user. What the user is really interested in is to have an indication of 
what the narrowed portion is for commands, and what is the narrowing 
state (permanent, one-shot, or inactive).
This indication may be done with reverse video like for TMM, or it may 
be done otherwise, notably by displaying only the narrowed portion as 
with command C-x n n.

Note  for instance that with this approach "C-x n n" would set:
- the narrowing state to "permanent",
- the narrowing target to region
- and the method of indication to "displaying narrowed portion only"


Method of indication should be configurable independently from narrowing 
command scope, and it should be configurable in a way that indication is 
dependent on the narrowing target (whole buffer, page, region, etc...) 
and on the narrowing state (permanent, one-shot, or inactive). The state 
is important because for instance reverse video could be a good idea for 
one-shot state, but it would be painful for permanent.

This independence between the mode of operation itself, and indications 
to the user of what is the mode of operation is crucial for 
futureproofnew / flexibility w.r.t. different platforms. For instance 
some people may think in the future that this indication would be better 
by some letters in the Mode Line, or by some prompt in the Minibuffer.

Best regards,
          Vincent.


Alan Mackenzie a écrit :
> Hi, Emacs!
>
> I've criticised Transient Mark Mode somewhat in the last few days.  I
> therefore feel obliged to make a constructive suggestion as how to make
> it better.  Here is that suggestion:
>
> Analysing T-M-M, it seems to consist of 3 vaguely related features:
> (i) Disabling functions which operate on the region;
> (ii) Highlighting the region;
> (iii) Restricting the operation of some commands (e.g. M-x occur) to the
>   region when highlit, a sort of narrowing.
>
> Just as an aside, I think that terms like "active mark" and "activating
> the region" are unhelpful, and have caused confused thinking over the
> years.  Neither the mark nor the region is an agent - they don't DO
> anything, anymore than a milepost on a country road between two villages,
> or the road itself, do.  So I suggest we purge these terms from the code
> and manual.
>
>
> Feature (i) above, the one for which "Transient Mark Mode" is named,
> doesn't seem to be useful, so let's just remove it - the mark, once set,
> remains set, ditto for the region.  The variable mark-even-if-inactive is
> redundant, and can vanish (or be marked obsolete).
>
>
> Feature (ii) seems to be what people really want.  So let's rename the
> entire feature "Region Highlighting Mode".  The variable
> `region-highlighting-mode' should take the values nil, t, and possibly
> 'always, should there be anybody who wants the region always to be
> highlit.
>
> Region highlighting is switched on when the user types C-<space>, (?C-u)
> C-x C-x or M-@ or the like, or the "certain mouse commands".  There
> should be a command to switch it off (Keybinding C-u C-g, perhaps?).  I
> don't think a simple C-g should switch it off.  Highlighting should also
> be removed (via a before-change-function, possibly) when the buffer is
> changed.  I don't think it should be switched off on executing a random
> command.  For example, if you do M-: region-highlit, and see "t", the t
> should remain meaningful.
>
> "Momentary Transient Mark Mode" (there's tautology there ;-) should stay,
> but be renamed to "Explicit Region Highlighting", to indicated that the
> region gets highlit only when the user explicitly requests it via
> C-<space> C-<space> or C-u C-x C-x.
>
>
> Feature (iii) should be construed as "Wide area commands are restricted
> to the region when it is highlit", and should be an option independent of
> Region Highlighting Mode.  How about calling it
> `area-commands-on-highlit-region-flag'?  To use this feature when Region
> Highlighting is switched off, a user needs to set explicit region
> highlighting first.
>
>
> I think something like this design would be logically coherent, simple to
> document, implement and use, would have the features that people want,
> and be a vast improvement over the current Transient Mark Mode.
>
> What do others think?
>
>