unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Michal Sojka <sojkam1@fel.cvut.cz>
To: Tomi Ollila <tomi.ollila@iki.fi>, notmuch@notmuchmail.org
Subject: Re: [PATCH] emacs: Add customization group for replying
Date: Tue, 04 Sep 2012 18:29:02 +0200	[thread overview]
Message-ID: <87zk55n44x.fsf@steelpick.2x.cz> (raw)
In-Reply-To: <m2ligqnoap.fsf@guru.guru-group.fi>

On Tue, Sep 04 2012, Tomi Ollila wrote:
> On Tue, Sep 04 2012, Michal Sojka <sojkam1@fel.cvut.cz> wrote:
>
>> On Thu, Jul 26 2012, Michal Sojka wrote:
>>> When one wants to customize the format of reply message, there nothing
>>> to tell the user how to do it.  Without knowing that construction of
>>> reply buffer is actually implemented in the message package, it seems
>>> that replying cannot be customized.
>>>
>>> Because I was getting annoyed by the empty line the between citation
>>> line and the quoted message, I figured out that changing this is fairly
>>> easy when one knows what to customize.
>>>
>>> This patch adds notmuch-reply customization group that that contains
>>> references to the relevant customization options. The new group is easy
>>> to find as it is shown as a result of running "M-x customize-group RET
>>> notmuch RET".
>>
>> Ping.
>>
>> Any objections against applying?
>
> Nobody dares to say anything due to infamiliriaty of this spesific case ;/.
>
> I could not find any reference this has been made before.

It's at least documented at
http://www.gnu.org/software/emacs/manual/html_node/elisp/Group-Definitions.html

  The argument members is a list specifying an initial set of
  customization items to be members of the group. However, most often
  members is nil, and you specify the group's members by using the
  :group keyword when defining those members.

> I could not find any discussion about this issue.
>
> With little effort I could not extract the customization tree to
> stdout I could have attempted to grep whether there is same variable
> in many groups.

I tried to grep emacs sources and found the following:

(defgroup message '((user-mail-address custom-variable)
(defgroup gnus-message '((message custom-group))
(defgroup ps-print-printer '((lpr custom-group))
(defgroup customize '((widgets custom-group))
(defgroup font-lock '((jit-lock custom-group))

At least the first line corresponds exactly to what is proposed in my
patch.

Cheers,
-Michal

  reply	other threads:[~2012-09-04 16:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-26 13:58 [PATCH] emacs: Add customization group for replying Michal Sojka
2012-07-30  3:00 ` Jameson Graef Rollins
2012-09-04  7:35 ` Michal Sojka
2012-09-04  9:13   ` Tomi Ollila
2012-09-04 16:29     ` Michal Sojka [this message]
2012-09-05  6:48       ` Tomi Ollila
2012-09-06  8:10         ` Michal Sojka
2012-09-06  9:00           ` Tomi Ollila
2012-09-04 12:16   ` Michal Nazarewicz
2012-09-04 16:33     ` Michal Sojka
2012-09-04 17:20       ` Michal Nazarewicz

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

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zk55n44x.fsf@steelpick.2x.cz \
    --to=sojkam1@fel.cvut.cz \
    --cc=notmuch@notmuchmail.org \
    --cc=tomi.ollila@iki.fi \
    /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.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

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 read-only IMAP folder(s) and NNTP newsgroup(s).