From: Eli Zaretskii <eliz@gnu.org>
To: Toomas Rosin <toomas@rosin.ee>
Cc: 73951-done@debbugs.gnu.org
Subject: bug#73951: 29.4; 'what-cursor-position' reports SPC instead of TAB in term-mode
Date: Mon, 04 Nov 2024 21:52:36 +0200 [thread overview]
Message-ID: <86r07qu67v.fsf@gnu.org> (raw)
In-Reply-To: <3174.1730749046@localhost> (message from Toomas Rosin on Mon, 04 Nov 2024 21:37:26 +0200)
> From: Toomas Rosin <toomas@rosin.ee>
> cc: 73951@debbugs.gnu.org
> Comments: In-reply-to Eli Zaretskii <eliz@gnu.org>
> message dated "Sun, 03 Nov 2024 18:39:13 +0200."
> Date: Mon, 04 Nov 2024 21:37:26 +0200
>
> Eli Zaretskii <eliz@gnu.org> wrote:
>
> > Did you try setting indent-tabs-mode to a non-nil value?
>
> How could I not have thought of this! But yes, when I set `indent-tabs-mode' to `t' *before* pasting the function definition, and then run "type tawk" in terminal buffer and move point in line mode onto the tab character, `C-x =' says correctly that point is on TAB.
>
> I had `indent-tabs-mode' set to `nil' globally in my init.el; now I see that it is a good idea to leave `indent-tabs-mode' to `t' in terminal mode.
"M-x term" intentionally resets indent-tabs-mode to nil, with this
comment:
;; we do not want indent to sneak in any tabs
So if setting indent-tabs-mode non-nil suits you better, try to be on
the lookout for whatever problems the above comment might hint at; I
don't really understand what it wants to say (but then I don't use
"M-x term").
> I have no more questions. Thank you.
Thanks, I will therefore close this bug.
prev parent reply other threads:[~2024-11-04 19:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 16:35 bug#73951: 29.4; 'what-cursor-position' reports SPC instead of TAB in term-mode toomas
2024-10-22 17:40 ` Eli Zaretskii
2024-10-23 14:00 ` Toomas Rosin
2024-10-23 17:47 ` Eli Zaretskii
2024-11-03 15:50 ` Toomas Rosin
2024-11-03 16:39 ` Eli Zaretskii
2024-11-04 19:37 ` Toomas Rosin
2024-11-04 19:52 ` Eli Zaretskii [this message]
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=86r07qu67v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=73951-done@debbugs.gnu.org \
--cc=toomas@rosin.ee \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).