Gnus development mailing list
 help / color / mirror / Atom feed
From: Benjamin Rutt <rutt+news@cis.ohio-state.edu>
Subject: Katsumi Yamaoka's CVS update of gnus/lisp (73 files)
Date: Wed, 20 Feb 2002 22:53:57 -0500	[thread overview]
Message-ID: <a51r68$hjp$1@quimby2.netfonds.no> (raw)

I couldn't help but notice the following changelog on the gnus cvslog
group:

	* many files: Remove trailing whitespaces, replace spc+tab with
	tab, replace leading whitespaces with tabs.

Does this change suggest that gnus source code should be indented with
only tabs, not spaces, in the future?  I wasn't aware of any gnus code
conventions, but this sure looks like a step in that direction.

I think that by default, both emacsen generate a mixture of tabs and
spaces when the user hits the TAB key to indent in emacs-lisp-mode.
It is my understanding that using only tabs in emacs-lisp-mode would
(speaking for GNU emacs now) require changes to the variable
`tab-width' and `tab-stop-list'.  In other words, if all gnus
developers had to start using the "only indent using tabs" convention,
then it would require that every developer customized their
emacs-lisp-mode-hook, for example.

I'm just wondering, are there any gnus code conventions that pertain
to the "indent with tabs vs. spaces" issue, and if so, what are they?
-- 
Benjamin



             reply	other threads:[~2002-02-21  3:53 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-21  3:53 Benjamin Rutt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-21  3:53 Benjamin Rutt
2002-02-21  4:28 ` Katsumi Yamaoka
2002-02-21  4:28 ` Katsumi Yamaoka
2002-02-21 14:04   ` Benjamin Rutt
2002-02-21 14:04   ` Benjamin Rutt
2002-02-21 17:27     ` Kai Großjohann
2002-02-21 17:27     ` Kai Großjohann
2002-02-21 23:47     ` Katsumi Yamaoka
2002-02-22  0:04       ` Paul Jarc
2002-02-22  0:04       ` Paul Jarc
2002-02-22  1:18       ` Benjamin Rutt
2002-02-22  2:50         ` Katsumi Yamaoka
2002-02-22  2:50         ` Katsumi Yamaoka
2002-02-22  9:04           ` Per Abrahamsen
2003-01-02  2:37           ` Lars Magne Ingebrigtsen
2002-02-22  1:18       ` Benjamin Rutt
2002-02-21 23:47     ` Katsumi Yamaoka
2002-02-21 23:48     ` Paul Jarc
2002-02-21 23:48     ` Paul Jarc
2002-02-21 23:47   ` Paul Jarc
2002-02-22  0:04     ` Katsumi Yamaoka
2002-02-22  0:04     ` Katsumi Yamaoka
2002-02-21 23:47   ` Paul Jarc

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='a51r68$hjp$1@quimby2.netfonds.no' \
    --to=rutt+news@cis.ohio-state.edu \
    /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).