unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: goncholden via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 55862@debbugs.gnu.org
Subject: bug#55862: Removing indent-tabs-mode set to t by default
Date: Thu, 09 Jun 2022 14:05:49 +0000	[thread overview]
Message-ID: <O-BKPoVOGJZg2fVI-ioMVIM1SFraclkIkELbHolFsBLnO6h38EtRPOXwoTOb22tDhaj3cWLMYkXANdi19n-NRX3oyXdavUaZgmBGUTcSU_w=@protonmail.com> (raw)
In-Reply-To: <83leu62d6e.fsf@gnu.org>

A 2016 survey by Felipe Hoffa concluded that spaces far outpace tabs in every major programming language with the exceptions of C, one of the very oldest programming languages, and Google's Go.

It is worth reconsidering the decision to stick with tabs in future.  I do not know of any mechanism to show (with some symbol) the beginning of each tab and the end of a line when space happens at the end of a line.

https://hoffa.medium.com/400-000-github-repositories-1-billion-files-14-terabytes-of-code-spaces-or-tabs-7cfe0b5dd7fd#.o7n8zeezx


------- Original Message -------
On Friday, June 10th, 2022 at 1:12 AM, Eli Zaretskii <eliz@gnu.org> wrote:


> > Date: Thu, 09 Jun 2022 12:40:35 +0000
> > From: goncholden goncholden@protonmail.com
> > Cc: 55862@debbugs.gnu.org
> >
> > > Of course, arguing about defaults is many times futile, since changing
> > > them is very easy.
> >
> > It is not so easy because one also has to make the change based on major mode.
>
>
> Every major mode has a mode hook, and the usual way to customize a
> mode is in that hook.





  reply	other threads:[~2022-06-09 14:05 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09  3:19 bug#55862: Removing indent-tabs-mode set to t by default goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-09  5:38 ` Eli Zaretskii
2022-06-09 12:40   ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-09 13:00     ` Lars Ingebrigtsen
2022-06-09 13:34       ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-09 13:38         ` Lars Ingebrigtsen
2022-06-09 15:53         ` Eli Zaretskii
2022-06-09 13:12     ` Eli Zaretskii
2022-06-09 14:05       ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-06-09 16:03         ` Eli Zaretskii
2022-06-09 16:06         ` Drew Adams
2022-06-09 16:35           ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-09 14:11     ` Dmitry Gutov
2022-06-09 14:18       ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-09 14:30         ` Dmitry Gutov
2022-06-09 14:10   ` Dmitry Gutov
2022-06-09 14:21     ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-09 16:06       ` Eli Zaretskii
2022-06-09 16:32         ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-09 16:52           ` Eli Zaretskii
2022-06-09 16:44         ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-09 16:58           ` Eli Zaretskii
2022-06-09 17:41     ` Drew Adams

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='O-BKPoVOGJZg2fVI-ioMVIM1SFraclkIkELbHolFsBLnO6h38EtRPOXwoTOb22tDhaj3cWLMYkXANdi19n-NRX3oyXdavUaZgmBGUTcSU_w=@protonmail.com' \
    --to=bug-gnu-emacs@gnu.org \
    --cc=55862@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=goncholden@protonmail.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).