From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Spaces rather than tabs by a major mode hook
Date: Fri, 10 Jun 2022 09:41:43 +0300 [thread overview]
Message-ID: <837d5p10m0.fsf@gnu.org> (raw)
In-Reply-To: <ry35hHB-H2eeS292S6qlJrL-UORGMr9WNqFhZlhjRHOwA853EQ8jlQw8b2T7lfBV5ZYzk6SdrWvgAV0aw1qPqqTIi9LJMGs518H4bajsK2w=@protonmail.com> (message from goncholden on Fri, 10 Jun 2022 05:46:44 +0000)
> Date: Fri, 10 Jun 2022 05:46:44 +0000
> From: goncholden <goncholden@protonmail.com>
> Cc: help-gnu-emacs@gnu.org
>
> > > The TAB key is usually bound to some indentation command such as indent-according-to-mode. So bind that to some other key and TAB to self-insert-command.
> >
> >
> > Or use "C-q TAB" to insert a literal TAB no matter what command TAB is
> > bound to.
>
> A superior choice would be to all TAB to be a tab by default, rather than binding to some other thing, making the key non-functional. RETURN could introduce indentation, but with the tab
> key introducing a literal tab.
No, that would be a step back. TAB is important because it re-indents
the current line, so you don't need to type RET and insert a newline
if all you want is re-indentation.
It is a relatively rare situation where you need to insert a literal
TAB, so having it bound to self-insert-command would be much less
useful than its current binding.
I think your current views are because you are trying to fight Emacs
features instead of using them to your benefit. Why do you need to
insert literal TABs so much? You never explained that.
next prev parent reply other threads:[~2022-06-10 6:41 UTC|newest]
Thread overview: 113+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 13:58 Spaces rather than tabs by a major mode hook goncholden via Users list for the GNU Emacs text editor
2022-06-09 15:12 ` Yuri Khan
2022-06-09 15:30 ` goncholden
2022-06-09 15:46 ` Yuri Khan
2022-06-09 16:08 ` goncholden
2022-06-09 16:34 ` Yuri Khan
2022-06-10 23:17 ` Emanuel Berg
2022-06-11 0:05 ` goncholden
2022-06-11 7:35 ` Eli Zaretskii
2022-06-09 18:13 ` goncholden
2022-06-09 19:15 ` [External] : " Drew Adams
2022-06-09 19:16 ` Drew Adams
2022-06-09 19:24 ` Tassilo Horn
2022-06-09 19:40 ` goncholden
2022-06-09 19:54 ` Tassilo Horn
2022-06-10 5:39 ` Eli Zaretskii
2022-06-10 5:46 ` goncholden
2022-06-10 6:08 ` Po Lu
2022-06-10 6:11 ` goncholden
2022-06-10 6:31 ` tomas
2022-06-10 6:41 ` Eli Zaretskii [this message]
2022-06-10 7:42 ` goncholden
2022-06-10 7:50 ` Eli Zaretskii
2022-06-10 8:31 ` goncholden
2022-06-10 10:49 ` Eli Zaretskii
2022-06-10 18:10 ` goncholden
2022-06-10 19:33 ` Eli Zaretskii
2022-06-10 19:40 ` goncholden
2022-06-10 19:44 ` Eli Zaretskii
2022-06-10 19:52 ` goncholden
2022-06-10 19:56 ` goncholden
2022-06-11 7:20 ` Eli Zaretskii
2022-06-11 7:30 ` Emanuel Berg
2022-06-11 7:57 ` tomas
2022-06-11 8:26 ` goncholden
2022-06-11 15:35 ` Emanuel Berg
2022-06-11 7:19 ` Eli Zaretskii
2022-06-11 8:17 ` goncholden
2022-06-11 8:40 ` Eli Zaretskii
2022-06-11 8:57 ` goncholden
2022-06-11 10:10 ` Eli Zaretskii
2022-06-11 10:20 ` goncholden
2022-06-11 10:33 ` Eli Zaretskii
2022-06-11 11:15 ` goncholden
2022-06-11 11:50 ` Eli Zaretskii
2022-06-11 20:02 ` goncholden
2022-06-12 2:24 ` [External] : " Drew Adams
2022-06-12 3:16 ` goncholden
2022-06-12 6:06 ` Eli Zaretskii
2022-06-12 6:40 ` goncholden
2022-06-12 7:02 ` Eli Zaretskii
2022-06-12 7:49 ` goncholden
2022-06-12 8:06 ` Po Lu
2022-06-12 8:35 ` goncholden
2022-06-12 6:40 ` Eli Zaretskii
2022-06-12 7:29 ` goncholden
2022-06-12 6:53 ` Po Lu
2022-06-12 7:06 ` goncholden
2022-06-12 7:18 ` Po Lu
2022-06-12 7:54 ` goncholden
2022-06-12 18:13 ` Netiquette is way to go Jean Louis
2022-06-12 23:25 ` goncholden
2022-06-13 4:53 ` Jean Louis
2022-06-13 6:25 ` goncholden
2022-06-13 6:26 ` Emanuel Berg
2022-06-13 7:17 ` Po Lu
2022-06-13 7:41 ` Emanuel Berg
2022-06-13 7:43 ` Jean Louis
2022-06-13 9:18 ` goncholden
2022-06-13 9:29 ` Po Lu
2022-06-13 10:39 ` goncholden
2022-06-13 11:48 ` Eli Zaretskii
2022-06-13 13:17 ` goncholden
2022-06-13 21:05 ` Emanuel Berg
2022-06-14 4:43 ` tomas
2022-06-14 10:08 ` Emanuel Berg
2022-06-13 15:42 ` [External] : " Drew Adams
2022-06-12 7:13 ` Spaces rather than tabs by a major mode hook Po Lu
2022-06-12 7:29 ` Eli Zaretskii
2022-06-12 8:29 ` goncholden
2022-06-12 8:36 ` Eli Zaretskii
2022-06-12 9:14 ` goncholden
2022-06-12 8:45 ` Po Lu
2022-06-12 9:02 ` goncholden
2022-06-12 18:21 ` Jean Louis
2022-06-12 23:29 ` goncholden
2022-06-13 3:03 ` Emanuel Berg
2022-06-13 5:39 ` Jean Louis
2022-06-13 6:24 ` Emanuel Berg
2022-06-13 6:33 ` goncholden
2022-06-13 15:17 ` [External] : " Drew Adams
2022-06-12 17:10 ` Jean Louis
2022-06-12 20:18 ` goncholden
2022-06-12 20:41 ` goncholden
2022-06-12 22:42 ` Jean Louis
2022-06-13 6:18 ` goncholden
2022-06-13 6:18 ` Emanuel Berg
2022-06-13 15:17 ` [External] : " Drew Adams
2022-06-13 11:55 ` Andreas Röhler
2022-06-13 12:12 ` goncholden
2022-06-11 10:39 ` goncholden
2022-06-11 21:00 ` Dmitry Gutov
2022-06-11 21:17 ` goncholden
2022-06-11 21:36 ` Dmitry Gutov
2022-06-11 21:56 ` goncholden
2022-06-12 0:07 ` goncholden
2022-06-12 0:19 ` Dmitry Gutov
2022-06-12 0:35 ` goncholden
2022-06-12 1:05 ` goncholden
2022-06-11 4:58 ` Emanuel Berg
2022-06-11 14:53 ` [External] : " Drew Adams
2022-06-11 15:39 ` Emanuel Berg
2022-06-10 23:03 ` Emanuel Berg
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=837d5p10m0.fsf@gnu.org \
--to=eliz@gnu.org \
--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).