unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 74775@debbugs.gnu.org
Subject: bug#74775: [PATCH] Update browse-url-kde variables
Date: Sat, 14 Dec 2024 00:54:20 +0200	[thread overview]
Message-ID: <33545.9225623467$1734130543@news.gmane.org> (raw)
In-Reply-To: <86ed2czqa2.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 12 Dec 2024 20:53:41 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Björn Bidar <bjorn.bidar@thaodan.de>
>> Cc: 74775@debbugs.gnu.org
>> Date: Thu, 12 Dec 2024 18:44:44 +0200
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> >> > Installing on master doesn't need to delve into these issues, since if
>> >> > we are wrong, we have enough time for users to holler and for us to
>> >> > fix.  Emacs 30, OTOH, is very close to the release, so we must be very
>> >> > certain this change cannot cause any trouble.
>> >> 
>> >> I don't think there's a chance for that.
>> >
>> > Famous last words...
>> 
>> KDE3 isn't used anymore even if so any release after has significantly
>> by more users.
>> Why support KDE3? 
>
> Because it is completely legitimate for people running old systems
> with KDE3 to want to install a new Emacs.

It is a strange thought to not apply a fix for less old or current
system just because potentially some person might install the next
Emacs release on a almost 20 year old system. 


>> >> If you decide to install the change on Emacs 30. Do you want me to send
>> >> the patch again with the changes mentioned by you i.e. defcustom version
>> >> and type?
>> >
>> > I still think we should install this on master.  AFAIK, we had exactly
>> > zero complaints about these defaults, perhaps for the simple reason
>> > that it is easy to customize a user option if its default is wrong for
>> > a user.
>> 
>> Most users would probably set the `browse-url-browser-function' or the
>> default detected happens to be the right default function.
>
> Sorry, I couldn't understand what you want to say here.

I'm saying that this issue doesn't come up to most users because they
change these options before trying to use the defaults in this instance.





  reply	other threads:[~2024-12-13 22:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8734ivrvfr.fsf@>
2024-12-11 12:38 ` bug#74775: [PATCH] Update browse-url-kde variables Eli Zaretskii
2024-12-11 14:03   ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-11 14:28     ` Robert Pluim
2024-12-11 16:14     ` Eli Zaretskii
2024-12-11 17:41       ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-11 19:07         ` Eli Zaretskii
2024-12-12 16:44           ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-12 18:53             ` Eli Zaretskii
2024-12-13 22:54               ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
     [not found] <6758c999.050a0220.38af58.bd51SMTPIN_ADDED_BROKEN@mx.google.com>
2024-12-11  1:22 ` Stefan Kangas
2024-12-10 23:04 Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors

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='33545.9225623467$1734130543@news.gmane.org' \
    --to=bug-gnu-emacs@gnu.org \
    --cc=74775@debbugs.gnu.org \
    --cc=bjorn.bidar@thaodan.de \
    --cc=eliz@gnu.org \
    /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).