unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jens Schmidt <jschmidt4gnu@vodafonemail.de>
Cc: 66780@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#66780: [PATCH] Improve rectangle-mark-mode when transient-mark-mode is off
Date: Sat, 28 Oct 2023 19:47:34 +0300	[thread overview]
Message-ID: <83a5s2d789.fsf@gnu.org> (raw)
In-Reply-To: <87v8aq3dr2.fsf@sappc2.fritz.box> (message from Jens Schmidt on Sat, 28 Oct 2023 18:36:49 +0200)

> From: Jens Schmidt <jschmidt4gnu@vodafonemail.de>
> Cc: Stefan Kangas <stefankangas@gmail.com>,  66780@debbugs.gnu.org
> Date: Sat, 28 Oct 2023 18:36:49 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > And that is something that doesn't automatically follows from your
> > personal preferences and use patterns.  It needs more serious
> > justifications.
> 
> It's not only my "personal preferences and use patterns".  See Sean's
> bug#42663 plus Michael's bug#16066.  So every now and then somebody
> having transient-mark-mode switched off comes across this.

Yes, I know.  But that doesn't remove the need to justify a change to
Emacs.

> > Why do you insist on making these changes in upstream, to
> > affect everyone else [...]
> 
> It's not "everyone else".  My solution of adding a conditional minor
> mode lighter has been designed to specifically affect (== help) only
> those that do not use permanent transient-mark-mode.

It's one more minor mode with one more lighter.  So yes, it affects
everyone else.

> > You found something that you'd
> > like to fix for your own reasons.
> 
> Really?  Go through all that effort of carefully describing the issue
> and discussing with you just for my own reasons, where I have (indeed)
> fixed that issue in my .emacs in 10mins?
> 
> > Once again I ask: why not
> > make these changes, or others that you propose, in your own local
> > Emacs, and be done?
>                       ^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> That's a rather discouraging request.  Is is somewhat in contrast to
> this statements from the README:
> 
>   You may encounter bugs in this release.  If you do, please report
>   them; your bug reports are valuable contributions to the FSF, since
>   they allow us to notice and fix problems on machines we don't have, or
>   in code we don't use often.
> 
> So are you asking me not to file any bugs?

Of course not.  But please don't expect us to agree with and accept
every change you suggest.  Each one of them is judged on its own
right, and not all of them will find their way into Emacs.  Sometimes,
we will not even agree that what you consider a bug is indeed a bug.

> Or, in other words: Which of my change requests so far had truly the
> quality to affect me and only me?

Are you asking about the 3 suggestions in this bug report?  Then I
think I already answered that: the first 2 I tend not to accept, the
last one I think could be accepted, and I'd like to hear opinions of
others about it.





  reply	other threads:[~2023-10-28 16:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-27 20:31 bug#66780: [PATCH] Improve rectangle-mark-mode when transient-mark-mode is off Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-28  6:24 ` Eli Zaretskii
2023-10-28 10:50   ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-28 10:58     ` Eli Zaretskii
2023-10-28 12:51       ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-28 13:17         ` Eli Zaretskii
2023-10-28 16:36           ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-28 16:47             ` Eli Zaretskii [this message]
2023-10-28 18:30               ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-28 18:48                 ` Eli Zaretskii
2023-10-29 14:49                   ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-02  6:33                     ` Eli Zaretskii

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=83a5s2d789.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=66780@debbugs.gnu.org \
    --cc=jschmidt4gnu@vodafonemail.de \
    --cc=stefankangas@gmail.com \
    /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).