From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 48058@debbugs.gnu.org, gusbrs.2016@gmail.com
Subject: bug#48058: tab-width's docstring
Date: Fri, 30 Apr 2021 05:20:12 -0500 [thread overview]
Message-ID: <CADwFkmkDQ3TT-9wV8M264vE=+yA79B8ZJv4_VnTWVfiRNj-Fcw@mail.gmail.com> (raw)
In-Reply-To: <83eeescka4.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> I propose the following text instead:
>
> Distance between tab stops (for display of tab characters), in columns.
>
> This controls the width of a TAB character on display.
> The value should be a positive integer.
> Note that this variable doesn't necessarily affect the size of the
> indentation step, but if the major mode's indentation facility
> inserts one or more TAB characters, this variable will affect the
> indentation step as well, even if `indent-tabs-mode' is non-nil.
Perhaps we could divide the last sentence up to make it easier to read?
Note that this variable doesn't necessarily affect the size of the
indentation step. However, if the major mode's indentation facility
normally inserts one or more TAB characters, this variable will
affect the indentation step as well, even if `indent-tabs-mode' is
non-nil.
Otherwise LGTM, please install.
next prev parent reply other threads:[~2021-04-30 10:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 13:11 bug#48058: tab-width's docstring Gustavo Barros
2021-04-27 13:53 ` Eli Zaretskii
2021-04-27 14:40 ` Gustavo Barros
2021-04-27 15:02 ` Eli Zaretskii
2021-04-27 15:14 ` Gustavo Barros
2021-04-27 15:32 ` Eli Zaretskii
2021-04-29 17:05 ` Stefan Kangas
2021-04-29 17:35 ` Eli Zaretskii
2021-04-29 20:14 ` Gustavo Barros
2021-04-29 22:53 ` Stefan Kangas
2021-04-30 0:44 ` Gustavo Barros
2021-04-30 7:18 ` Eli Zaretskii
2021-04-30 10:20 ` Stefan Kangas [this message]
2021-04-30 10:49 ` Eli Zaretskii
2021-04-30 12:00 ` Gustavo Barros
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkmkDQ3TT-9wV8M264vE=+yA79B8ZJv4_VnTWVfiRNj-Fcw@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=48058@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gusbrs.2016@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.