From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: Problem with agent and empty groups
Date: Sat, 06 Mar 2004 16:40:28 +0900 [thread overview]
Message-ID: <yotl65di779v.fsf@jpl.org> (raw)
In-Reply-To: <uishjs1fr.fsf@xpediantsolutions.com>
>>>>> In <uishjs1fr.fsf@xpediantsolutions.com>
>>>>> Kevin Greiner <kgreiner@xpediantsolutions.com> wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
> >>>>>> In <u4qt4bwkb.fsf@xpediantsolutions.com>
> >>>>>> Kevin Greiner <kgreiner@xpediantsolutions.com> wrote:
> >
> >> I've checked in a new version that blocks recording nil entries.
> >
> > I wonder what indentation function you use to edit ELisp files.
> > Those are shifted from the standard, and tabs were replaced with
> > spaces...
> Hmmm... Well, I usually work on projects where nobody will agree on
> the development environment so I have indent-tabs-mode defaulted to
> nil. Let's see, OK I now have a hook to set it to t for lisp files.
That's ok. Although I don't like mixture of indent by setting
indent-tabs-mode as nil and indent by default.
> As for shifted, I've opened a couple of files that I've never worked
> on then tried to re-indent using indent-sexp. Nothing changed so my
> indentation settings (i.e. the defaults) appear to be what other
> people are using. Perhaps it was the spaces that were throwing the
> alignment off. Please let me know if the standard isn't the default
> emacs settings.
I see. Your setting may not be strange, but you perhaps didn't
use the indent function. See the following:
(defun gnus-request-accept-article (group &optional gnus-command-method last
[...]
(let ((gnus-command-method (or gnus-command-method
(gnus-find-method-for-group group)))
(result (funcall (gnus-get-function gnus-command-method 'request-accept-article)
(if (stringp group) (gnus-group-real-name group) group)
(cadr gnus-command-method)
last)))
IMO, that is unsightly. Furthermore, it will have a bad
influence on additional changes of the future. I can see many
non-standard indentations in some files in Gnus. Weren't they
made from the same cause?
--
Katsumi Yamaoka <yamaoka@jpl.org>
next prev parent reply other threads:[~2004-03-06 7:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 17:20 David S Goldberg
2004-02-09 17:26 ` David S Goldberg
2004-02-09 22:56 ` Kevin Greiner
2004-02-13 21:03 ` David S Goldberg
2004-02-23 17:34 ` David S Goldberg
2004-02-24 23:05 ` Kevin Greiner
2004-02-25 21:59 ` David S Goldberg
2004-03-04 12:56 ` Kevin Greiner
2004-03-04 15:12 ` Katsumi Yamaoka
2004-03-05 16:28 ` Kevin Greiner
2004-03-06 7:40 ` Katsumi Yamaoka [this message]
2004-03-05 17:02 ` David S Goldberg
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=yotl65di779v.fsf@jpl.org \
--to=yamaoka@jpl.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).