unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: 55991@debbugs.gnu.org
Subject: bug#55991: 29.0.50; Wish list: detect and ask user if to change indentation or settings
Date: Thu, 16 Jun 2022 06:55:57 +0300	[thread overview]
Message-ID: <YqqpzUF4CBOK/DRo@protected.localdomain> (raw)
In-Reply-To: <86mtee4h9e.fsf@protected.rcdrun.com>

For clarification:

"old source files" -- are those made in older times, most often with
different editors, different indentation styles, in different
programming languages.

"new style" -- it is relevant only to such old source files, as Emacs
will automatically impose indentation

However, old source files shall sometimes remain how they are when
opened. There may cultural and habitual reason for the files to remain
not indented.

When user opens such old file, various modes in Emacs are going to
start enforcing the indentation on user.

Users should be warned if they should allow Emacs to change even those
invisible characters or if they should adopt the new indentation or
not when editing such files.

For example, instead of TABS, an Emacs mode may start enforcing
spaces without asking user. Other editor notepadqq asks user if that
change should take place.

1) It is possible to make function to recognize that file had tabs
   instead of spaces, and user should be asked about it.

2) It is possible to recognize that file was not indented by the
   mode's standard, and to ask user if new indentation should be
   adopted.

Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/





      reply	other threads:[~2022-06-16  3:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-15  5:39 bug#55991: 29.0.50; Wish list: detect and ask user if to change indentation or settings Jean Louis
2022-06-16  3:55 ` Jean Louis [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=YqqpzUF4CBOK/DRo@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=55991@debbugs.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.
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).