From: dalanicolai <dalanicolai@gmail.com>
To: Emacs Devel <emacs-devel@gnu.org>
Subject: (doc-view.el) Tabs or spaces convention?
Date: Wed, 19 Jan 2022 14:22:48 +0100 [thread overview]
Message-ID: <CACJP=3kYRxgQ=1zXVtYzox5V7iRcZAxUqW0a3LNj_QTjrV11aw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 314 bytes --]
It seems that doc-view.el is (still) full of tabs (I only discovered when I
wanted to make a commit,
and git errored). I will just convert all tabs to spaces unless that would
make me deviate from
some 'hidden' convention. In that case, please inform me about it. I wasn't
able to find any info
about it.
Thanks!
[-- Attachment #2: Type: text/html, Size: 417 bytes --]
next reply other threads:[~2022-01-19 13:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 13:22 dalanicolai [this message]
2022-01-19 14:03 ` (doc-view.el) Tabs or spaces convention? Robert Pluim
2022-01-19 14:41 ` Stefan Monnier
2022-01-19 21:41 ` Stefan Kangas
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='CACJP=3kYRxgQ=1zXVtYzox5V7iRcZAxUqW0a3LNj_QTjrV11aw@mail.gmail.com' \
--to=dalanicolai@gmail.com \
--cc=emacs-devel@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).