From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: problems with Emacs 28
Date: Sat, 24 Oct 2020 03:55:12 +0200 [thread overview]
Message-ID: <87tuukwfpb.fsf@zoho.eu> (raw)
In-Reply-To: 87r1poddpj.fsf@zoho.eu
> The byte-compiler, and the docstring, tells me I should use `map-put!'
> as `map-put' is decrepated. However when I do that, I get
> a "map-not-inplace" error.
>
> The Elisp in particular is this
>
> ;; remove troublesome Swedish and special chars from autokey
> ;; add more as needed
> (cl-loop
> for (r w)
> in `(("ä" "a")
> ("Ä" "A")
> ("å" "a")
> ("Å" "A")
> ("é" "e")
> ("ö" "o")
> ("Ö" "O")
> ("ń" "n")
> ("ś" "s") )
> do (map-put bibtex-autokey-titleword-change-strings r w) )
> ;; https://dataswamp.org/~incal/emacs-init/my-bibtex.el
>
> What is that bang (explication mark) syntax BTW?
Now this is the only error that remains. A Warning with `map-put'; an
error with `map-put!' (after complying with the warning's piece of
advice). (And again, what does the exclamation mark mean?)
The mysterious Emacs-w3m error was solved like this. It wasn't _my_
Emacs-w3m files it couldn't find, it was Emacs-w3m! That's right,
I got it from MELPA when I got the new Emacs, but forgot to add it to
the load path of the Makefile when byte compiling.
That is a bit annoying to do manually for each pack on installs,
actually. Why isn't the elpa/ recursively added to the load path?
--
underground experts united
http://user.it.uu.se/~embe8573
https://dataswamp.org/~incal
next prev parent reply other threads:[~2020-10-24 1:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 16:50 problems with Emacs 28 Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-23 17:33 ` Jean Louis
2020-10-23 18:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-23 18:00 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-24 1:55 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2020-10-24 12:56 ` Stefan Monnier
2020-10-24 12:57 ` Stefan Monnier
2020-10-24 9:46 ` Michael Heerdegen
2020-10-24 17:00 ` Drew Adams
2020-10-24 19:26 ` Michael Heerdegen
2020-10-24 22:11 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-24 22:08 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-25 12:13 ` Michael Heerdegen
2020-10-25 14:15 ` Drew Adams
2020-10-27 0:29 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-27 10:22 ` Michael Heerdegen
2020-10-28 16:21 ` Jens C. Jensen
2020-10-28 17:07 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-28 17:18 ` Stefan Monnier
2020-10-31 18:26 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-01 13:51 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-23 18:16 ` Eli Zaretskii
2020-10-23 18:22 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-23 18:44 ` Stefan Monnier
2020-10-24 0:13 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-23 19:09 ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-10-24 0:14 ` Emanuel Berg 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=87tuukwfpb.fsf@zoho.eu \
--to=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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).