[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Thu, 27 Sep 2018 17:26:01 +0000
On Thu, Sep 27, 2018 at 00:45:59 +0200, hw wrote:
> Alan Mackenzie <address@hidden> writes:
> > Hello, hw.
> > On Fri, Sep 21, 2018 at 22:28:53 +0200, hw wrote:
> >> address@hidden (Charles A. Roelli) writes:
> >> >> From: hw <address@hidden>
> >> >> Date: Wed, 19 Sep 2018 22:04:14 +0200
> >> >> With t-m-m disabled, there is no way to fortify the region, and there is
> >> >> no highlighting. Why would I disable it?
> > [ .... ]
> >> Disabling t-m-m doesn't make any sense at all. Why would anyone disable
> >> it?
> > For the avoidance of the complexities that dealing with
> > transient-mark-mode involves.
> Which complexities do you mean?
The ones I've outlined in previous posts to you. You've shown no sign in
the past of having understood what I've said. So I'll say it one last
time. This time please pay attention.
The complexity I'm referring to is having "modes" (like vi's insert and
command mode) in Emacs where a single command does different things
according to the mode. This happens with transient-mark-mode enabled,
the two modes being mark "active" and mark not "active". This complexity
is avoided by disabling transient-mark-mode.
[ .... ]
> > Your last suggestion borders on the offensive, since it suggests that
> > any user whose needs and understanding are different from yours
> > should not be taken into account in plotting the future of Emacs.
> It doesn't suggest that; it only suggests to remove functionality that
> is pointless and unnecessary and, along with it, a great deal of
> complexity and inconsistency which accompany it.
You _are_ becoming offensive. Your personal preferences are NOT
objective goodness. You have your way of using Emacs, and you should not
try to force it onto me. Thankfully, the maintainers of Emacs are not
about to remove the choice.
> Do you have an example of something that could not be accomplished with
> transient-mark-mode enabled and only with it disabled?
No, of course not. Any editing result can be achieved with t-m-m either
enabled or disabled. If you really were interested in simplicity, you
would be advocating abolishing transient-mark-mode completely. Emacs is
simpler without it, and still a full-featured editor (as it was in the
decades before transient-mark-mode was written). It would make lots of
users unhappy, though.
> > I do agree with you that transient-mark-mode is a hodge-podge of vaguely
> > related distinct features, mostly badly named, and that was why I argued
> > against it becoming a default setting some years ago.
> I didn't say that t-m-m is a hodge-podge.
Sorry, those were my words, not yours.
> > I also agree with you that these distinct features should be capable of
> > being en/disabled independently. These distinct features are (i) the
> > highlighting of the region; (ii) the disablement of commands which need
> > the mark to function;
> Do you mean it should be possible to disable commands that want the
> region to be active to do something?
No, I meant precisely what I wrote. I did not mention the region.
> That would at least need clarification of the intention, i. e. was the
> intention to limit them to the region, to extend them to the region, or
With transient-mark-mode disabled, you avoid this complexity. ;-)
> --- Commands are already disabled when t-m-m is enabled and
> mark-even-if-inactive is nil, so why do there need to be more ways to
> disable them?
Please read again what I wrote, and concentrate.
> Not that I, in theory, wouldn't appreciate a way to fortify the region
To WHAT the region? "Fortify" is not Emacs terminology.
> .... when t-m-m is disabled, but since there is no point in disabling
> it, ...
You are simply wrong on this point. I wish you would stop incessantly
> .... I don't see a need for one (But you could disable the mark, see
> Instead of voting for more ways to disable commands, ....
Nobody is advocating this.
> .... I might argue to remove the functions that imply "region" because
> implying to do stuff with a region is unnecessary when t-m-m is enabled
> because t-m-m means to do anything either with a region or not,
> depending on whether the region is active or not.
You would be better not so to argue.
> What's the point and the advantage of duplicating all commands that can
> do stuff with the contents of a buffer only because a fundamental design
> flaw makes it so inefficient to determine whether commands should do
> their things with the whole buffer or with a part of it by requiring the
> user to narrow and to widen the buffer in order to make that
Would you please stop insinuating that a feature of Emacs which you
happen not to like is a "fundamental design flaw". It is insulting to
generations of Emacs developers, and is not true. Your thinking it is
based on your lack of a deeper understanding of Emacs' design, purpose
> I don't understand why this wasn't simply overcome by setting the mark
> to nil. You could have *one* set of commands instead of several, and if
> you wanted them to do their things with the region, do not have the mark
> set to nil, and if you want them to work on the whole buffer, just set
> the mark to nil. You wouldn't need t-m-m then, would you (except for
> the highlighting)?
Setting the mark to nil at any time would reduce its effectiveness for
> > (iii) the "narrowing" of the buffer for certain
> > commands (such as M-%).
> Is narrowing the buffer sometimes disabled?
> How do you determine to which parts you want to narrow buffers to
> without selecting either the relevant parts or the irrelevant parts?
C-x n n narrow-to-region (after setting mark and moving point); or
C-x n d narrow-to-defun; or
C-x n p narrow-to-page.
And when you're finishied,
C-x n w widen.
> >> Without highlighting, a different indicator could be useful to show
> >> whether the region is active or not, like a hint in the mode line.
> > Yes. I suggest this should be a single character, or at most two
> > characters. Space in the mode line is precious. Maybe "+" could fulfil
> > this role somewhere.
> Right, though '+' would make me think that there is more to display
> while there isn't, like because there isn't enough room for it.
> Changing the colour of the mode line might work, too.
I suppose so. Though I'd be more in favour of changing the colour of
just a small part of the mode line, to minimise the reduction in
Alan Mackenzie (Nuremberg, Germany).
Re: delete-selection-mode as default (WAS: Some developement questions), Phil Sainty, 2018/09/07
RE: delete-selection-mode as default (WAS: Some developement questions), Drew Adams, 2018/09/07
Re: delete-selection-mode as default (WAS: Some developement questions), Yuri Khan, 2018/09/07
- Re: visual-region-mode?, (continued)
- Re: visual-region-mode?, hw, 2018/09/19
- Re: visual-region-mode?, Charles A. Roelli, 2018/09/20
- Re: visual-region-mode?, hw, 2018/09/21
- Re: visual-region-mode?, Charles A. Roelli, 2018/09/24
- Re: visual-region-mode?, Yuri Khan, 2018/09/24
- RE: visual-region-mode?, Drew Adams, 2018/09/24
- Re: visual-region-mode?, hw, 2018/09/26
- Re: visual-region-mode?, Alan Mackenzie, 2018/09/24
- Re: visual-region-mode?, Charles A. Roelli, 2018/09/26
- Re: visual-region-mode?, hw, 2018/09/26
- Re: visual-region-mode?,
Alan Mackenzie <=
- Re: visual-region-mode?, Juri Linkov, 2018/09/12
- Re: delete-selection-mode as default, Dmitry Gutov, 2018/09/08
- Re: delete-selection-mode as default, Elias Mårtenson, 2018/09/09
- Re: delete-selection-mode as default, Clément Pit-Claudel, 2018/09/09