Gnus development mailing list
 help / color / mirror / Atom feed
From: Benjamin Rutt <rutt+news@cis.ohio-state.edu>
Subject: Re: Katsumi Yamaoka's CVS update of gnus/lisp (73 files)
Date: Thu, 21 Feb 2002 09:04:14 -0500	[thread overview]
Message-ID: <a52v0l$a1c$1@quimby2.netfonds.no> (raw)
In-Reply-To: <yosuu1sbwjae.fsf@jpl.org>

Katsumi Yamaoka <yamaoka@jpl.org> writes:

>> 	* many files: Remove trailing whitespaces, replace spc+tab with
>> 	tab, replace leading whitespaces with tabs.
>
> `replace leading whitespaces with tabs' does not mean using only
> tabs.  I've replaced
>
> ssssssss -> t
> sssssssst -> tt
>
> and so on.  I've never done something like: ttss -> ttt

OK.  That wasn't obvious from your Changelog, since you mention
"spc+tab" which generally sounds like "all combinations of spaces and
tabs" being replaced with tab.

> It is natural on the condition that the option `indent-tabs-mode' is
> t (by default).  Could you see the actual Gnus source files?

OK, I cvs updated one file, and saved the old version first
(gnus-dired.el, a file I wrote not too long ago) to see the diffs.
What is the motivation for this change?

When I wrote gnus-dired.el, the last thing I did before submitting it
for inclusion was M-x mark-whole-buffer and M-x indent-region, and
I've never customized any of the indention variables in
emacs-lisp-mode either.  So, gnus-dired.el was originally indented
using emacs's default indentation in emacs-lisp-mode.  Is there any
way I could have coded it differently to avoid requiring your
whitespace modification?  If not, then I think you're going to have to
repeat the changes you made again and again as new code is submitted
using emacs-lisp-mode's default indentation rules.
-- 
Benjamin



  parent reply	other threads:[~2002-02-21 14:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-21  3:53 Benjamin Rutt
2002-02-21  4:28 ` Katsumi Yamaoka
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-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:48     ` Paul Jarc
2002-02-21 23:48     ` Paul Jarc
2002-02-21 14:04   ` Benjamin Rutt [this message]
2002-02-21 23:47   ` 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  4:28 ` Katsumi Yamaoka
  -- strict thread matches above, loose matches on Subject: below --
2002-02-21  3:53 Benjamin Rutt

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='a52v0l$a1c$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).