zsh-users
 help / color / mirror / code / Atom feed
From: Marc Chantreux <marc.chantreux@ulpmm.u-strasbg.fr>
To: Oliver Kiddle <okiddle@yahoo.co.uk>
Cc: zsh-users@sunsite.dk
Subject: Re: can't run _email-mutt
Date: Thu, 2 Jun 2005 14:37:18 +0200	[thread overview]
Message-ID: <20050602123718.GA21218@xpeerience.u-strasbg.fr> (raw)
In-Reply-To: <13199.1117464233@trentino.groupinfra.com>

le 30/05/2005,
Oliver Kiddle nous écrivait :
> Ah, the problem is probably related to the section of _email-addresses
> starting with the comment "# get list of all plugins except any with
> missing config files". For the builtin plugins, it excludes those for
> which it doesn't find a config file. It's perhaps a new change to mutt
> that .muttrc can also be .mutt/muttrc. Can it have other names?

i wasn't skilled enought in zsh to understand those lines. thanks for
explains.

you're right : i've added .mutt/muttrc to the list and it works fine
now.

i've just seen in the mutt man that a system-wide configuration file
exists too : /etc/Muttrc

so, there are 3 configuration files :

~/.muttrc
~/.mutt/muttrc
/etc/Muttrc
              
> We could probably do with a more sophisticated plugin for mutt aliases,
> however. I assume you've got some form of include directives to pull in
> aliases from all those other files. Any idea how we could get a full
> list of mutt aliases?

well, the simplest way is to use an extern program that does it well :

lbdbq | sed -n '/alias/{s/\(^[^  ]\+\).*alias\(.*\)/\2:\1/;p}'

or something like that.

a pure zsh solution is trying to parse all files that are sourced (
using the source command ) by .muttrc.

regards

mc


  reply	other threads:[~2005-06-02 12:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-27 14:16 Marc Chantreux
2005-05-30  9:18 ` Oliver Kiddle
2005-05-30 13:57   ` Marc Chantreux
2005-05-30 14:43     ` Oliver Kiddle
2005-06-02 12:37       ` Marc Chantreux [this message]
2005-06-02 12:59         ` Oliver Kiddle

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=20050602123718.GA21218@xpeerience.u-strasbg.fr \
    --to=marc.chantreux@ulpmm.u-strasbg.fr \
    --cc=okiddle@yahoo.co.uk \
    --cc=zsh-users@sunsite.dk \
    /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://git.vuxu.org/mirror/zsh/

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).