unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: 47784@debbugs.gnu.org
Subject: bug#47784: 27.2: ses-header-row [PATCH INCLUDED]
Date: Fri, 07 May 2021 13:14:03 +0200	[thread overview]
Message-ID: <87h7jevls4.fsf@gnus.org> (raw)
In-Reply-To: <20210506101615.bkko5xqirskhvs2a@E15-2016.optimum.net> (Boruch Baum's message of "Thu, 6 May 2021 06:16:15 -0400")

Boruch Baum <boruch_baum@gmx.com> writes:

> But I don't ever want a tab, ever, in any document that I work on, ever.

That's counter to how Emacs sources are (and should remain).  We use a
mix of tabs and spaces (but the spaces are after the tabs).

> If tabs are needed in order to be compatible with upstream then I'd want
> emacs to untabify on read and tabify on export.

I don't think there's any such functionality in Emacs, but it shouldn't
be difficult for you to hack up something like that to fix up your
patches.  It would be easier if you just didn't change your tab/space
settings when you work on Emacs sources, though.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2021-05-07 11:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-15  3:31 bug#47784: 27.2: ses-header-row [PATCH INCLUDED] Boruch Baum
2021-04-17 19:30 ` Eli Zaretskii
2021-04-19  9:24   ` Boruch Baum
2021-04-19 13:03     ` Eli Zaretskii
2021-04-19 13:27       ` Boruch Baum
2021-04-21  0:02       ` Stefan Kangas
2021-04-21  9:23         ` Eli Zaretskii
2021-05-05 13:08 ` Lars Ingebrigtsen
2021-05-05 16:40   ` Boruch Baum
2021-05-05 19:15     ` Eli Zaretskii
2021-05-05 19:40       ` Boruch Baum
2021-05-05 19:46         ` Eli Zaretskii
2021-05-06  8:10           ` Robert Pluim
2021-05-06 11:05             ` Boruch Baum
2021-05-06  8:17     ` Lars Ingebrigtsen
2021-05-06 10:16       ` Boruch Baum
2021-05-07 11:14         ` Lars Ingebrigtsen [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=87h7jevls4.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=47784@debbugs.gnu.org \
    --cc=boruch_baum@gmx.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).