unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: uzibalqa <uzibalqa@proton.me>
To: Drew Adams <drew.adams@oracle.com>
Cc: Robert Pluim <rpluim@gmail.com>,
	"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>,
	Eli Zaretskii <eliz@gnu.org>
Subject: RE: [External] : Re: Making new menu after Tools using keymap-set-after
Date: Wed, 19 Jul 2023 17:37:37 +0000	[thread overview]
Message-ID: <NZ5hvupNPHetJZErJs5Bhakc7wr9xGH8vPZqwgojyOgXpPpIOQzFGuevMognwS75eG6vcqrO8RbkxnqKCXCIxSadpz1vSFyqekDcH0NReNQ=@proton.me> (raw)
In-Reply-To: <SJ0PR10MB548832D62BB9984AF179A085F339A@SJ0PR10MB5488.namprd10.prod.outlook.com>


------- Original Message -------
On Thursday, July 20th, 2023 at 5:28 AM, Drew Adams <drew.adams@oracle.com> wrote:


> > GNU Emacs 29.0.50
> > 
> > Why is it so difficult to know the snapshot version after doing
> > a clone or a checkout on master. Rather than just emacs, can the
> > directory produced include the version (e.g. emacs-29.0.50).
> 
> 
> Why does a new Elisp learner prefer to use
> an unreleased pretest version of Emacs?

To test that the menu with the new keymap-set-after I am using works. 
 
> Seems like asking for additional trouble,
> with not so much ability to tell whether
> something is a new-feature bug or part of
> what Emacs has long done (tried and true,
> tested and well-used).
> 
> Like learning to drive in a test version
> of a new car. Maybe exciting, but maybe
> not so great for learning what's what -
> can't tell what's intended from what just
> happens to be part of a not-fully-baked
> current implementation.

It is not so much fun, I admit.
 
> Why not learn Emacs using the latest
> release, Emacs 28.2?



  reply	other threads:[~2023-07-19 17:37 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18 16:04 Making new menu after Tools using keymap-set-after uzibalqa
2023-07-18 16:29 ` Eli Zaretskii
2023-07-18 16:56   ` uzibalqa
2023-07-18 17:12     ` Eli Zaretskii
2023-07-18 17:29       ` uzibalqa
2023-07-18 18:28         ` Eli Zaretskii
2023-07-18 18:45           ` uzibalqa
2023-07-18 19:02             ` Eli Zaretskii
2023-07-18 19:26               ` uzibalqa
2023-07-19  2:25                 ` Eli Zaretskii
2023-07-19  8:08                   ` uzibalqa
2023-07-19  9:10                     ` Robert Pluim
2023-07-19 15:58                       ` uzibalqa
2023-07-19 16:33                         ` Eli Zaretskii
2023-07-19 16:37                           ` uzibalqa
2023-07-19 16:44                           ` Robert Pluim
2023-07-19 16:54                             ` uzibalqa
2023-07-19 17:07                               ` Robert Pluim
2023-07-19 17:11                                 ` uzibalqa
2023-07-19 17:25                                   ` Platon Pronko
2023-07-19 17:34                                     ` uzibalqa
2023-07-20  3:17                                       ` Platon Pronko
2023-07-19 17:28                               ` [External] : " Drew Adams
2023-07-19 17:37                                 ` uzibalqa [this message]
2023-07-19 19:00                                   ` Drew Adams
2023-07-19 19:08                                     ` uzibalqa
2023-07-20  3:32                                       ` Platon Pronko
2023-07-20  8:43                                         ` uzibalqa
2023-07-19 21:00                           ` uzibalqa
2023-07-18 20:42             ` [External] : " Drew Adams
2023-07-18 20:55               ` uzibalqa
2023-07-18 21:40                 ` uzibalqa
2023-07-19 12:11                   ` Eli Zaretskii
2023-07-19 11:58               ` Eli Zaretskii
2023-07-19 14:18                 ` Drew Adams
2023-07-18 20:49       ` uzibalqa
2023-07-19 12:00         ` 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='NZ5hvupNPHetJZErJs5Bhakc7wr9xGH8vPZqwgojyOgXpPpIOQzFGuevMognwS75eG6vcqrO8RbkxnqKCXCIxSadpz1vSFyqekDcH0NReNQ=@proton.me' \
    --to=uzibalqa@proton.me \
    --cc=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    --cc=rpluim@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.
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).