unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Gustavo Barros <gusbrs.2016@gmail.com>
Cc: 48058@debbugs.gnu.org
Subject: bug#48058: tab-width's docstring
Date: Tue, 27 Apr 2021 18:32:21 +0300	[thread overview]
Message-ID: <83y2d3hhfe.fsf@gnu.org> (raw)
In-Reply-To: <87tunrkbdi.fsf@gmail.com> (message from Gustavo Barros on Tue, 27 Apr 2021 12:14:50 -0300)

> From: Gustavo Barros <gusbrs.2016@gmail.com>
> Cc: 48058@debbugs.gnu.org
> Date: Tue, 27 Apr 2021 12:14:50 -0300
> 
> I didn't expect anything different to happen.  It is just that 
> `tab-width' is determining more than just the "display width of the TAB 
> character": if you (or the major-mode for you) are indenting with spaces 
> the content of the buffer is different according to `tab-width', it not 
> just a matter of "display".
> 
> But I see your point, and perhaps the docstring is clearer to someone 
> more seasoned than myself, and avoids other pitfalls along the way which 
> I do not even see.  Hopefully, it will feel just as clear to me someday. 
> ;-)

Fair enough, let's see if there are other opinions about this.





  reply	other threads:[~2021-04-27 15:32 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 [this message]
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
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

  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=83y2d3hhfe.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=48058@debbugs.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 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).