unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Boruch Baum <boruch_baum@gmx.com>
To: Robin Tarsiger <rtt@dasyatidae.com>
Cc: Emacs-Devel List <emacs-devel@gnu.org>
Subject: Re: Support Q: How many args for self-insert-command
Date: Mon, 18 Jan 2021 08:47:27 -0500	[thread overview]
Message-ID: <20210118134727.dkvg7tufdi4ilvgx@E15-2016.optimum.net> (raw)
In-Reply-To: <3b17a61a-2a30-92e3-2d81-3e77b7ee6f65@dasyatidae.com>

Thanks, Robin. I don't have the local resources for an emacs git
repository to be able to do what you did, and debian says that
installing their Emacs27 from their testing repository will introduce
'grave' bugs with ssh/libcrypt/poppler/... packages.

On 2021-01-18 06:55, Robin Tarsiger wrote:
> Boruch Baum wrote:
> > At what version did Emacs change the number of ARGs for
> > self-insert-command?
> >
> > I only have available versions 26 (one arg) and a September v28-snapshot
> > (two args), so this is really asking about the state at release version
> > 27 (still not available to me in debian).
>
> Here's an answer with implied pointers to sources for similar answers:
>
> git annotate shows that a relevant line in cmds.c was changed by
> commit 81f0e05 on 2018-11-17, with the log entry:
>
>   * src/cmds.c (Fself_insert_command): Get last-command-event via (new) arg.
>
> The diff for that commit shows that it also adds an entry to etc/NEWS
> under "Lisp Changes in Emacs 27.1".
>
> To confirm from a different perspective, the Emacs 27.1 I'm using from
> Arch has the two-argument form.
>
> -RTT

--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1  7286 0036 9E45 1595 8BC0



  reply	other threads:[~2021-01-18 13:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18 11:34 Support Q: How many args for self-insert-command Boruch Baum
2021-01-18 12:55 ` Robin Tarsiger
2021-01-18 13:47   ` Boruch Baum [this message]
2021-01-18 14:14     ` Basil L. Contovounesios
2021-01-18 15:00       ` Boruch Baum
2021-01-18 15:21         ` Basil L. Contovounesios
2021-01-18 16:39       ` Stefan Monnier
2021-01-18 17:19 ` Drew Adams

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=20210118134727.dkvg7tufdi4ilvgx@E15-2016.optimum.net \
    --to=boruch_baum@gmx.com \
    --cc=emacs-devel@gnu.org \
    --cc=rtt@dasyatidae.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 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).