all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Goh <andrewgoh95@yahoo.com.sg>
Cc: 63536@debbugs.gnu.org
Subject: bug#63536: Feature Request
Date: Wed, 17 May 2023 16:37:24 +0300	[thread overview]
Message-ID: <83bkijxenf.fsf@gnu.org> (raw)
In-Reply-To: <1884442844.2472195.1684329429592@mail.yahoo.com> (message from Andrew Goh on Wed, 17 May 2023 13:17:09 +0000 (UTC))

[PLEASE use Reply All to have the bug tracker on the CC list.]

> Date: Wed, 17 May 2023 13:17:09 +0000 (UTC)
> From: Andrew Goh <andrewgoh95@yahoo.com.sg>
> 
> Updates of GNU Emacs.  Many software tools out in the proprietary world have such a feature.

So you want a command to check whether a newer Emacs is available?
But where should this command look?  Many (most?) people install
precompiled binaries prepared by their distros, and I assume those
distros have their "check for updates" service or something?

We could check on the GNU FTP site, but how many users will want to
download and build Emacs from sources?

What do other people think about this?





  parent reply	other threads:[~2023-05-17 13:37 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 [this message]
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
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=83bkijxenf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=63536@debbugs.gnu.org \
    --cc=andrewgoh95@yahoo.com.sg \
    /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.