From: Eli Zaretskii <eliz@gnu.org>
To: Payas Relekar <relekarpayas@gmail.com>
Cc: 63536@debbugs.gnu.org, andrewgoh95@yahoo.com.sg
Subject: bug#63536: Feature Request
Date: Wed, 17 May 2023 20:16:18 +0300 [thread overview]
Message-ID: <831qjeyj31.fsf@gnu.org> (raw)
In-Reply-To: <87o7mjyrng.fsf@gmail.com> (message from Payas Relekar on Wed, 17 May 2023 19:34:06 +0530)
> From: Payas Relekar <relekarpayas@gmail.com>
> Cc: Andrew Goh <andrewgoh95@yahoo.com.sg>, 63536@debbugs.gnu.org
> Date: Wed, 17 May 2023 19:34:06 +0530
>
> The idea itself is valid, as long as the update check happens only at
> explicit user action. The command should only compare current version of
> Emacs with the latest update and inform user about the difference. Then
> the onus is on user to proceed with the update. Command output can point
> them to relevant section of the manual, informing of ways to install
> (and also update) Emacs.
How will we know where to look? That's the main technical issue with
this, I think.
Another possible issue is whether just to tell the user "A newer
version XY.Z is available, you can download it at <URL>", or also
offer a possibility of actually downloading the newer version?
next prev parent reply other threads:[~2023-05-17 17:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1553770628.2069339.1684237196253.ref@mail.yahoo.com>
2023-05-16 11:39 ` bug#63536: Feature Request Andrew Goh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-16 15:46 ` Eli Zaretskii
[not found] ` <2050007547.2204916.1684290974957@mail.yahoo.com>
2023-05-17 10:58 ` Eli Zaretskii
[not found] ` <1884442844.2472195.1684329429592@mail.yahoo.com>
2023-05-17 13:37 ` Eli Zaretskii
2023-05-17 16:53 ` Jim Porter
2023-05-19 13:36 ` Benjamin Riefenstahl
2023-05-17 14:04 ` Payas Relekar
2023-05-17 17:16 ` Eli Zaretskii [this message]
2023-05-17 15:40 ` Payas Relekar
2023-05-17 15:51 ` Payas Relekar
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=831qjeyj31.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=63536@debbugs.gnu.org \
--cc=andrewgoh95@yahoo.com.sg \
--cc=relekarpayas@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 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.