From: Eli Zaretskii <eliz@gnu.org>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>
Cc: 74775@debbugs.gnu.org
Subject: bug#74775: [PATCH] Update browse-url-kde variables
Date: Sat, 14 Dec 2024 10:19:28 +0200 [thread overview]
Message-ID: <86ed2awub3.fsf@gnu.org> (raw)
In-Reply-To: <87ttb7qjmr.fsf@> (message from Björn Bidar on Sat, 14 Dec 2024 00:54:20 +0200)
> From: Björn Bidar <bjorn.bidar@thaodan.de>
> Cc: 74775@debbugs.gnu.org
> Date: Sat, 14 Dec 2024 00:54:20 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> 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.
That's not the reason: we will apply the change to master without any
delays. The reason not to install this in Emacs 30 is because Emacs
30 will be released VSN, and we don't have any time to get feedback
from people who might be adversely affected by this change, even
though we consider such breakage unlikely. Installing on master
allows us ample time for collecting such feedback, or deciding by lack
thereof that the change cannot break anything.
> >> 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.
In which case this is not urgent, and installing on master should be
enough.
Thanks.
next prev parent reply other threads:[~2024-12-14 8:19 UTC|newest]
Thread overview: 13+ 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
[not found] ` <87ttb7qjmr.fsf@>
2024-12-14 8:19 ` Eli Zaretskii [this message]
2024-12-14 8:21 ` Eli Zaretskii
[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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86ed2awub3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74775@debbugs.gnu.org \
--cc=bjorn.bidar@thaodan.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.