From: Katsumi Yamaoka <yamaoka@jpl.org>
To: larsi@gnus.org
Cc: ding@gnus.org
Subject: untabify Lisp sources (was Re: closing all inactive server connections)
Date: Tue, 31 Jul 2007 11:58:09 +0900 [thread overview]
Message-ID: <b4mhcnlb7pa.fsf_-_@jpl.org> (raw)
In-Reply-To: <m2ps29oq7k.fsf@lifelogs.com>
Hi Lars, I wish you to respond.
>>>>> Ted Zlatanov wrote:
TZ> Unfortunately there were tabs in the gnus-srvr.el file (aren't we
TZ> supposed to use untabify?) so the patch comes out too long.
KY> I cannot understand what you want to do. gnus-srvr.el in the CVS
KY> trunk uses tabs for the indentations that require eight or more
KY> characters width (except for only one line). The reason the patch
KY> is big should be that you, some program or other untabified them.
KY> Do you think that it should be applied to all the Gnus sources?
KY> I don't agree. IMO, whoever changes the Gnus sources should use
KY> the default value for the `indent-tabs-mode' variable.
> I was told by Lars a while ago to use untabify on Gnus commits, so I do
> as a general rule. That's what I mean by my question "aren't we
> supposed to use untabify?"
Oops. I might have overlooked it in this list. But I don't see
an advantage of untabifying the indentations. What is the reason
(if it exists) to force all the Gnus developers to alter the default
value of `indent-tabs-mode' or to use a hook that runs when CVS
committing?
> I didn't know the convention had changed, that's all. I'm happy to
> stick with whatever is the current convention. Let me know if you want
> me to commit the change, or if you'll commit your version instead.
I can agree with the new convention if there is a good reason.
But even if the convention changes (or had changed?), I think
that we should separately do untabifying of the Lisp sources and
installing of changes.
Regards,
next prev parent reply other threads:[~2007-07-31 2:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-07 15:59 closing all inactive server connections Ted Zlatanov
2007-07-10 19:54 ` Ted Zlatanov
2007-07-19 13:46 ` Ted Zlatanov
2007-07-27 17:06 ` Ted Zlatanov
2007-07-28 0:18 ` Ted Zlatanov
2007-07-30 6:22 ` Katsumi Yamaoka
2007-07-30 15:39 ` Ted Zlatanov
2007-07-31 2:57 ` Katsumi Yamaoka
2007-07-31 3:08 ` Katsumi Yamaoka
2007-07-31 3:19 ` Ted Zlatanov
2007-07-31 8:52 ` Katsumi Yamaoka
2007-08-02 19:51 ` Ted Zlatanov
2007-08-15 11:28 ` Simon Josefsson
2007-08-16 7:18 ` Katsumi Yamaoka
2007-08-16 7:25 ` Katsumi Yamaoka
2007-08-16 9:49 ` Simon Josefsson
2007-08-16 15:35 ` Ted Zlatanov
2007-08-16 15:32 ` Ted Zlatanov
2007-08-16 15:56 ` Ted Zlatanov
2007-08-16 23:19 ` Katsumi Yamaoka
2007-08-16 23:25 ` Ted Zlatanov
2007-08-16 23:47 ` Katsumi Yamaoka
2007-08-17 11:09 ` Katsumi Yamaoka
2007-09-10 14:52 ` Ted Zlatanov
2007-08-15 18:28 ` Reiner Steib
2007-07-31 3:16 ` Ted Zlatanov
2007-07-31 3:19 ` Katsumi Yamaoka
2007-07-31 2:58 ` Katsumi Yamaoka [this message]
2007-07-31 22:05 ` untabify Lisp sources Reiner Steib
2007-08-01 2:44 ` Ted Zlatanov
2007-07-31 22:57 ` Miles Bader
2007-08-01 2:46 ` Ted Zlatanov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b4mhcnlb7pa.fsf_-_@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
--cc=larsi@gnus.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 NNTP newsgroup(s).