From: Jean Louis <bugs@gnu.support>
To: help-gnu-emacs@gnu.org, Robert Pluim <rpluim@gmail.com>,
Tatsu Takamaro <tatsu.takamaro@gmail.com>
Subject: Re: Remapping keys and creating my own keymap \\ too complicated\\
Date: Fri, 06 Dec 2024 13:38:17 +0300 [thread overview]
Message-ID: <A7184E02-D85A-4C20-9AF7-1E5EBA7DA4F4@gnu.support> (raw)
In-Reply-To: <87o71pb0bz.fsf@gmail.com>
On December 6, 2024 12:57:36 PM GMT+03:00, Robert Pluim <rpluim@gmail.com> wrote:
>>>>>> On Thu, 5 Dec 2024 21:08:41 +0300, Tatsu Takamaro <tatsu.takamaro@gmail.com> said:
>
> Tatsu> I gave a link to an article in my original message. Here it is:
> Tatsu> https://emacspal.com/extending-emacs-functionally-with-user-defined-keymaps/
>
>Ah, Iʼd missed that.
>
>I object to a lot of the advice given in that article (and the other
>articles on that site are equally objectionable or inaccurate), so Iʼd
>recommend you avoid it.
>
>Robert
There is page about the global visual line mode which speaks about the global editing over all files at once which is factually totally incorrect. Visual line mode is used for the word wrap and not global editing over files.
That page was generated by neglectful artificial intelligence.
Jean
next prev parent reply other threads:[~2024-12-06 10:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 16:59 Remapping keys and creating my own keymap \\ too complicated\\ Tatsu Takamaro
2024-12-04 7:43 ` Jean Louis
2024-12-04 15:49 ` Tatsu Takamaro
2024-12-04 15:55 ` Tatsu Takamaro
2024-12-04 16:06 ` Robert Pluim
2024-12-04 16:37 ` Tatsu Takamaro
2024-12-04 16:40 ` Robert Pluim
2024-12-04 17:05 ` Tatsu Takamaro
2024-12-05 10:25 ` Robert Pluim
2024-12-05 18:08 ` Tatsu Takamaro
2024-12-06 9:57 ` Robert Pluim
2024-12-06 10:38 ` Jean Louis [this message]
2024-12-06 13:18 ` Robert Pluim
2024-12-08 16:16 ` Tatsu Takamaro
2024-12-08 23:07 ` Stephen Berman
2024-12-09 22:34 ` Tatsu Takamaro
2024-12-04 16:25 ` Jean Louis
2024-12-04 16:57 ` Tatsu Takamaro
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=A7184E02-D85A-4C20-9AF7-1E5EBA7DA4F4@gnu.support \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
--cc=rpluim@gmail.com \
--cc=tatsu.takamaro@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).