From: goncholden <goncholden@protonmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Spaces rather than tabs by a major mode hook
Date: Sun, 12 Jun 2022 07:29:04 +0000 [thread overview]
Message-ID: <1xWltEpBCXM4OToWWQOprTzAT-58faY8YWEcWTYC5dZASb8_nOPTl9VjOMD-L4V7cEXW3ez45L7ApXd-BQdTxrtUKKCWldskV6ZNHfT2TTU=@protonmail.com> (raw)
In-Reply-To: <83leu2wfjy.fsf@gnu.org>
------- Original Message -------
On Sunday, June 12th, 2022 at 6:40 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Sat, 11 Jun 2022 20:02:57 +0000
> > From: goncholden goncholden@protonmail.com
> > Cc: help-gnu-emacs@gnu.org
> >
> > > Emacs requires you to customize, once, the indentation so that it
> > > could thereafter help you by indenting everything automatically to
> > > suit the indentation style. That's a win by any measure.
Unless you don't want help. You want to do it yourself.
Basically, I want all of the support disabled and take complete control except of the language highlighting.
> > That the problem you are taking ages to understand. "Emacs requires you to customize", the origin of the problem.
>
>
> No, it isn't the problem. It is the solution to many problems,
> whereby people use many different coding styles in their programs. It
> is impossible to provide good indentation support for any arbitrary
> style, so if you happen to need to work with non-standard style, you
> need to tell Emacs about that style.
But my point is different. I want to instruct emacs not to provide me with good indentation support for the current buffer, as I know better what to do. This is the argument I am putting forward.
> > > > The question about how many columns should each construct be indented, has no answer.
> > >
> > > It should be possible to answer that question by just examining the
> > > file you posted.
> >
> > No, because there are thousands of files.
>
>
> Are they using different styles? If so, my suggestion is to reformat
> them to the default style supported by Emacs out of the box, before
> you start editing.
Yes. Same language with many different styles and all syntactically and operationally correct. So fixing for
some specific style has no practical value whatsoever.
> > > Alternatively, you could just reindent the entire file according to
> > > the defaults, like this:
> > >
> > > C-x h
> > > C-M-\
> > >
> > > and then keep making changes without any customizations.
> >
> > That would destroy the possibilities of easily detecting code changes.
>
>
> Detecting code changes is nowadays the job of a VCS. A modern VCS can
> easily show you changes other than whitespace changes. Or you can
> commit the reformatted but otherwise unchanged source first, and then
> examine the changes relative to that.
>
> > The mantra that things can always be customised implies observance to a single formatting scheme. Legacy code does not even subscribe to that. They only had simple editors. If I introduce tabs with
> > "C-q TAB", all those tabs get removed by emacs as soon as one presses return at the end of the line.
> >
> > Emacs is acting like a dictator.
>
>
> If Emacs doesn't satisfy your needs, you are free to use another
> editor, aren't you?
It is not about satisfying my needs. There exist regulations in the world and I cannot modify an entire codebase because some want to use an editor over another. Currently I cannot successfully present my case for the use of emacs with the other service branches. Capish, my dear Eli?
next prev parent reply other threads:[~2022-06-12 7:29 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
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 [this message]
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='1xWltEpBCXM4OToWWQOprTzAT-58faY8YWEcWTYC5dZASb8_nOPTl9VjOMD-L4V7cEXW3ez45L7ApXd-BQdTxrtUKKCWldskV6ZNHfT2TTU=@protonmail.com' \
--to=goncholden@protonmail.com \
--cc=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).