Gnus development mailing list
 help / color / mirror / Atom feed
From: Nick Papadonis <nick@yahoo.com.com>
Cc: Per Abrahamsen <abraham@dina.kvl.dk>, ding@gnus.org
Subject: Re: integrating x-face stuff
Date: 12 Jan 2001 17:46:09 -0500	[thread overview]
Message-ID: <m37l40qthq.fsf@h0050bad6338d.ne.mediaone.net> (raw)
In-Reply-To: <vaf8zogwhv1.fsf@lucy.cs.uni-dortmund.de>

    > On 11 Jan 2001, Nick Papadonis wrote:
    >> However, I can't agree with you on it being quite simple.  I
    >> looked through the info files and saw nothing on this.

    > Which part of M-x customize-option RET message-default-headers
    > RET did you not know about?  The part of invoking Customize to
    > change options?  Or the fact that the option in question is
    > called message-default-headers?

    > In fact, the variable in question is mentioned in the node
    > `Message Headers' in the `message' info file (not the Gnus info
    > file).

    > kai -- Be indiscrete.  Do it continuously.
My prev. message: 'Why can't an X-face file be specified in 'customize->gnus'?  Since
they are displayed in gnus, shouldn't people be able to configure
which one to send.' -> I understand customize.

Yes, I did not know about message-default-headers.
Excuse me if I didn't read through every info file for each of
X-Emacs's lisp packages.  I simply installed gnus, read all it's info files, and was
never pointed towards the message info file.  I don't know every
internal working of gnus, nor should I have to.

Let this not be an argument, but an attempt at bettering gnus and it's
documentation.  As seen in my previous post, I have not been the only
one misled here.

Maybe this doesn't even have to do with gnus.  I'm not a maintainer
so, this isn't my call.

-- 
- Nick



  reply	other threads:[~2001-01-12 22:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-11  4:08 Nick Papadonis
2001-01-11  9:52 ` Per Abrahamsen
2001-01-11 10:02   ` Nick Papadonis
2001-01-11 11:28     ` Per Abrahamsen
2001-01-11 22:30       ` Nick Papadonis
2001-01-12 21:52         ` Kai Großjohann
2001-01-12 22:00     ` Kai Großjohann
2001-01-12 22:46       ` Nick Papadonis [this message]
2001-01-12 22:53         ` Charles Sebold
2001-01-12 23:13           ` Jack Twilley
2001-01-12 23:31         ` Kai Großjohann
2001-01-13 12:29           ` Nick Papadonis
     [not found]   ` <86ae8x5zf1.fsf@blowfish.brfmasthugget.se>
2001-01-12 11:50     ` Per Abrahamsen
2001-01-12 11:52       ` Per Abrahamsen

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=m37l40qthq.fsf@h0050bad6338d.ne.mediaone.net \
    --to=nick@yahoo.com.com \
    --cc=abraham@dina.kvl.dk \
    --cc=ding@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).