unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: define-key upon common-lisp-mode and inferior-lisp-mode
Date: Tue, 30 Aug 2022 17:25:48 +0200	[thread overview]
Message-ID: <Yw4r/N6nJfU/OvOo@tuxteam.de> (raw)
In-Reply-To: <4Ay4NyY90a27uk-ntZfTWEDj1acAwD_FoEIesw88aCV705DTqT2G0T3fXkUbO5YDAkFdvwlQHft0Xa0Jjn3UfOPwVfm01OoyEoBDzioT_pc=@proton.me>

[-- Attachment #1: Type: text/plain, Size: 822 bytes --]

On Tue, Aug 30, 2022 at 02:15:51PM +0000, uzibalqa wrote:
> ------- Original Message -------
> On Tuesday, August 30th, 2022 at 1:49 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> 
> 
> > > Date: Tue, 30 Aug 2022 13:22:48 +0000
> > > From: uzibalqa uzibalqa@proton.me
> > > Cc: help-gnu-emacs@gnu.org
> > > 
> > > Have got "Lisp error: (void-function local-define-key)" for "Emacs 27.2".
> > 
> > 
> > Use local-set-key instead.
> > 
> > > On the other modes I have been using
> > > 
> > > (define-key emacs-lisp-mode-map (kbd "H-e") #'eval-last-sexp)
> > > 
> > > The last seems more standard for many modes.
> > 
> > 
> > I can only show you the better solutions, I cannot force you use them.
> 
> What can be the origin of the Lisp Error?

What does the error message say, again?

Cheers
-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2022-08-30 15:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30  4:59 define-key upon common-lisp-mode and inferior-lisp-mode wilnerthomas--- via Users list for the GNU Emacs text editor
2022-08-30 11:44 ` Eli Zaretskii
2022-08-30 12:26   ` uzibalqa
2022-08-30 12:51     ` Eli Zaretskii
2022-08-30 13:22       ` uzibalqa
2022-08-30 13:49         ` Eli Zaretskii
2022-08-30 14:15           ` uzibalqa
2022-08-30 15:25             ` tomas [this message]
2022-08-30 18:21               ` wilnerthomas--- via Users list for the GNU Emacs text editor
2022-08-30 18:41                 ` tomas
2022-08-30 19:08                   ` wilnerthomas--- via Users list for the GNU Emacs text editor
2022-08-31 12:11                     ` Alessandro Bertulli
2022-08-30 16:24             ` Eli Zaretskii
2022-08-31 12:04           ` Alessandro Bertulli
2022-08-31 12:42             ` Eli Zaretskii
2022-09-01  9:27               ` Alessandro Bertulli
2022-08-30 13:24 ` Stefan Monnier via Users list for the GNU Emacs text editor

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=Yw4r/N6nJfU/OvOo@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=help-gnu-emacs@gnu.org \
    /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).