From: 황병희 <soyeomul@doraji.xyz>
To: help-gnu-emacs@gnu.org
Subject: Re: help my chromebook backspace key destroy
Date: Sun, 17 Oct 2021 15:11:52 +0900 [thread overview]
Message-ID: <87czo4dvtj.fsf@penguin> (raw)
In-Reply-To: <87pms4p8p6.fsf@telefonica.net> ("Óscar Fuentes"'s message of "Sun, 17 Oct 2021 06:38:13 +0200")
Óscar Fuentes <ofv@wanadoo.es> writes:
> [...]
> But the OP would be better served if he/she remaps the keys at a lower
> level. A quick web search gives
>
> https://ictsolved.github.io/remap-key-in-linux/
>
> which addresses the specific case of remapping a broken DEL key under X
> (apparently that key breaks often.)
Hellow Óscar!
I agree with your comments. Next time i will study it, thanks!
Sincerely, Gnus fan Byung-Hee
next prev parent reply other threads:[~2021-10-17 6:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 4:01 help my chromebook backspace key destroy 황병희
2021-10-17 4:13 ` Solved (Was: Re: help my chromebook backspace key destroy) 황병희
2021-10-17 4:21 ` help my chromebook backspace key destroy Eduardo Ochs
2021-10-17 4:38 ` Óscar Fuentes
2021-10-17 6:11 ` 황병희 [this message]
2021-10-17 6:02 ` 황병희
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=87czo4dvtj.fsf@penguin \
--to=soyeomul@doraji.xyz \
--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).