all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Xavier Maillard <xavier@maillard.im>
To: Robert Pluim <rpluim@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Use BBDB for `rmail-output' ?
Date: Fri, 8 Jun 2018 17:07:16 +0200	[thread overview]
Message-ID: <201806081507.w58F7Gdd001468@localhost.localdomain> (raw)
In-Reply-To: <87efhh63g3.fsf@gmail.com> (message from Robert Pluim on Fri, 08 Jun 2018 11:19:08 +0200)

a> From: Robert Pluim <rpluim@gmail.com>
> Mail-Copies-To: never
> Date: Fri, 08 Jun 2018 11:19:08 +0200
> Content-Type: text/plain
> Cc: help-gnu-emacs@gnu.org
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> Date: Fri, 8 Jun 2018 06:56:19 +0200
> >> From: Xavier Maillard <xavier@maillard.im>
> >> 
> >> I want to hack something around BBDB and Rmail. The goal is to use a
> >> BBDB field eg. `rmail-ouput' as the target name for the function
> >> `rmail-output' function.
> >> 
> >> AFAIK, I do not see anything to do that without a piece of advice.
> >
> > You mean, if the basic requirement is to make no changes at all to
> > rmail-out itself?  In that case, you are probably right, but why would
> > we self-impose such a restriction?  If we want to support BBDB, why
> > not modify rmail-out to be capable of such support?
> >
> > (I admit I don't understand what exactly is entailed in "using a BBDB
> > field as a target name", so perhaps if you elaborate on that, we will
> > find some way of doing that without changing rmailout.el.)
> 
> I suspect Xavier is talking about setting the output filename for
> rmail-output based on a BBDB field.

Exactly. Instead of setting `rmail-output-file-alist' (which is much
more complex since one must have REGEXP knowledge), I'd rather want to
add a BBDB field.

> I subscribe to the 'big ball of emails in a single folder' theory
> myself, since searching is easy.

I am not opposed to this "theory" but I'd like to separate it a little
bit so that files do not become huge (which can be a pain at some
point). In majority, I am killing incoming messages as much as
possible (I only ouput things that I consider worth it for short/mid
or long term).

-- 
Xavier Maillard                      
e/j:xavier@maillard.im               w:www.maillard.im
m: 06 52 18 63 43
GPG: 9983 DCA1 1FAC 8DA7 653A  F9AA BA49 09B7 8F04 DE1B



  parent reply	other threads:[~2018-06-08 15:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-08  4:56 Use BBDB for `rmail-output' ? Xavier Maillard
2018-06-08  6:55 ` Eli Zaretskii
2018-06-08  9:19   ` Robert Pluim
2018-06-08  9:28     ` Eli Zaretskii
2018-06-08  9:38       ` Robert Pluim
2018-06-08 15:14         ` Xavier Maillard
2018-06-08 15:10       ` Xavier Maillard
2018-06-08 15:07     ` Xavier Maillard [this message]
2018-06-08 16:24       ` Robert Pluim
  -- strict thread matches above, loose matches on Subject: below --
2018-06-13  3:40 Roland Winkler

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=201806081507.w58F7Gdd001468@localhost.localdomain \
    --to=xavier@maillard.im \
    --cc=help-gnu-emacs@gnu.org \
    --cc=rpluim@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.