Re: Automatically encrypting to receipients based on the existance
On 08:30 Sat 26 Jan , Nicolas Rachinsky wrote: * Clay Barnes [EMAIL PROTECTED] [2008-01-25 22:07 -0700]: The subject pretty much says it all. I want to set mutt to automatically encrypt email to anyone who's email has a corresponding public key in the local gpg keyfile. I know that's more complex than the usual send-hook entails, but I think it'd be a pretty nifty way to avoid crafting and maintaining a ton of custom send-hook lines in my muttrc. http://www.rachinsky.de/nicolas/mutt.shtml That looks like a useful patch. Is it headed for main-line inclusion? -- Clay Barnes Website: http://www.hci-matters.com GPG Public Key: http://www.hci-matters.com/keys/claybarnes_public_key_until20080718.gpg signature.asc Description: Digital signature
Re: Leopard Migration Hammered Mutt
On Sat 26.Jan'08 at 13:02:26 -0500, Marc Vaillant wrote:
On Sat, Jan 26, 2008 at 05:13:11PM +, [EMAIL PROTECTED] wrote:
export shows:
PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
Mutt is in /sw/bin/
How can I add /sw/bin/ to my path?
put
export PATH=${PATH}:/sw/bin
in ~/.profile
You may want to try just typing /sw/bin/mutt first just to see if it
works properly after migration.
Raffi
Multiple IMAP accounts
Hello, i'm currently using two imap accounts with mutt (let's call them account A and account B). I set up accounthooks for each account to define spoolfiles, mbox, records etc. Mail is checked in all subscribed folders, but that's exaclty the problem i have. During startup mutt connects to account A and lists correctly all folders I'm subscribed to. New messages for all the mailboxes in account A are displayed. To see all subscribed folders and checks on new mail in account B won't work until I manually open one mailbox in account B. Is there any better way to have multiple accounts working in mutt? Something like an automatical connection to account B when starting mutt? My mutt version is 1.5.17, relevant parts of my mutt configuration: ## set imap_authenticators= set imap_delim_chars=/. set imap_keepalive=300 unset imap_list_subscribed set imap_passive set imap_peek set imap_servernoise set mail_check=60 set imap_check_subscribed # Account A set spoolfile=imap://localhost:6000/INBOX set record=imap://localhost:6000/sentmail set postponed=imap://localhost:6000/postponed set mbox=imap://localhost:6000/savedmail set folder=imap://localhost:6000/ account-hook . 'unset folder' account-hook . 'unset imap_pass' source ~/.mutt/accounthook_A #spoolfile etc source ~/.mutt/accounthook_B #inboxes for Account A and B mailboxes imaps://imap.gmail.com/INBOX imap://localhost:6000/INBOX ## Regargs, F. Unglaub.
Re: Automatically encrypting to receipients based on the existance
* Clay Barnes [EMAIL PROTECTED] [2008-01-26 10:57 -0700]: On 08:30 Sat 26 Jan , Nicolas Rachinsky wrote: http://www.rachinsky.de/nicolas/mutt.shtml That looks like a useful patch. Is it headed for main-line inclusion? Thank you. There hasn't been much feedback. Nicolas -- http://www.rachinsky.de/nicolas
Re: Multiple IMAP accounts
On Sun 27.Jan'08 at 12:41:52 +0100, Florian Unglaub wrote: Is there any better way to have multiple accounts working in mutt? Yes, there is! Unfortunately, mutt doesn't handle imap as well as it handles mbox and maildir. Therefore, I recommend using OfflineIMAP with mutt. Raffi
Re: Automatically encrypting to receipients based on the existance
On 17:24 Sun 27 Jan , Nicolas Rachinsky wrote: * Clay Barnes [EMAIL PROTECTED] [2008-01-26 10:57 -0700]: On 08:30 Sat 26 Jan , Nicolas Rachinsky wrote: http://www.rachinsky.de/nicolas/mutt.shtml That looks like a useful patch. Is it headed for main-line inclusion? Thank you. There hasn't been much feedback. Well, I really like it. I haven't exactly bug-tested it, but aside from that, I'd love to see it in mainline. -- Clay Barnes Website: http://www.hci-matters.com GPG Public Key: http://www.hci-matters.com/keys/claybarnes_public_key_until20080718.gpg signature.asc Description: Digital signature
Re: Automatically encrypting to receipients based on the existance
On Sun, Jan 27, 2008 at 05:24:36PM +0100, Nicolas Rachinsky wrote: * Clay Barnes [EMAIL PROTECTED] [2008-01-26 10:57 -0700]: On 08:30 Sat 26 Jan , Nicolas Rachinsky wrote: http://www.rachinsky.de/nicolas/mutt.shtml That looks like a useful patch. Is it headed for main-line inclusion? Thank you. There hasn't been much feedback. Nicolas I'd like it too, included it into the main-package... I'm using such constructs like your mentioned »source 'gpg --list-keys | perl -e ...« and was always waiting for a better solution. Thanks a lot! sigi signature.asc Description: Digital signature
Re: Automatically encrypting to receipients based on the existance
On Sun, Jan 27 2008, sigi wrote: On Sun, Jan 27, 2008 at 05:24:36PM +0100, Nicolas Rachinsky wrote: * Clay Barnes [EMAIL PROTECTED] [2008-01-26 10:57 -0700]: On 08:30 Sat 26 Jan , Nicolas Rachinsky wrote: http://www.rachinsky.de/nicolas/mutt.shtml That looks like a useful patch. Is it headed for main-line inclusion? Thank you. There hasn't been much feedback. Nicolas I'd like it too, included it into the main-package... I'm using such constructs like your mentioned »source 'gpg --list-keys | perl -e ...« and was always waiting for a better solution. Hello, I vote for it too! Cheers, Peter -- http://pmrb.free.fr/contact/
Re: Leopard Migration Hammered Mutt
On Monday, 28 January 2008 at 02:49, [EMAIL PROTECTED] wrote: Thanks, Your suggestion below pointed out that .bash_profile is the initialization file. But .bash_profile has no references to Path in it. I can add PATH=$PATH:/sw/bin as you suggested, but will adding this override my original Path variable, or simply add it to the existing path? If it is possible I would rather add /sw/bin to the resource file where the rest of my Path is stored. How would I go about doing this? http://www.finkproject.org/doc/users-guide/install.php?phpLang=en#setup (in short, source /sw/bin/init.sh in .bash_profile)
Re: Leopard Migration Hammered Mutt
Thanks, Your suggestion below pointed out that .bash_profile is the initialization file. But .bash_profile has no references to Path in it. I can add PATH=$PATH:/sw/bin as you suggested, but will adding this override my original Path variable, or simply add it to the existing path? If it is possible I would rather add /sw/bin to the resource file where the rest of my Path is stored. How would I go about doing this? Bill -- Original message -- From: Peter Münster [EMAIL PROTECTED] On Sat, Jan 26 2008, [EMAIL PROTECTED] wrote: PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin Mutt is in /sw/bin/ How can I add /sw/bin/ to my path? Hello, Just after logging in, you can enter the command ls -alrut, that shows in the last lines, the files that have just been read. Among these files, there should be an initialisation file for your shell, for example .bashrc or .profile. In the end of this file, you can put the line PATH=$PATH:/sw/bin (for a csh-like shell, the syntax is perhaps different...) Cheers, Peter
Re: Leopard Migration Hammered Mutt
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday, January 28 at 02:49 AM, quoth [EMAIL PROTECTED]: Your suggestion below pointed out that .bash_profile is the initialization file. But .bash_profile has no references to Path in it. I can add PATH=$PATH:/sw/bin as you suggested, but will adding this override my original Path variable, or simply add it to the existing path? It adds it to the existing path. Your Path is stored as a colon-separated list of folders containing programs (e.g. /bin:/usr/bin:/sbin:/usr/sbin). The string $PATH is a reference to the existing path---if you say echo $PATH your shell will print out your current PATH, because that's the string referred to be the notation $PATH. When you tell your shell to set a variable name to be something, it performs a similar kind of expansion. For example, if you say FOO=$PATH, the variable FOO will now contain a copy of the contents of the variable $PATH. You can append things to variable expansions, because the shell operates almost entirely in terms of lines of text. For example, if you say FOO=word, then the command echo $FOO will print out word. If you then say BAR=$FOO-plunkity, the BAR variable will consist of word-plunkity. A similar think would happen had you instead said FOO=$FOO-plunkity, which is that FOO would then be a reference to the text word-plunkity. Do you see how that works? Thus, the command suggested, PATH=$PATH:/sw/bin, will set the PATH to be a string consisting of whatever $PATH is (i.e. your current path), a colon, and the string /sw/bin. It will not throw away your existing path. If it is possible I would rather add /sw/bin to the resource file where the rest of my Path is stored. How would I go about doing this? That would be /etc/profile ~Kyle - -- It was luxuries like air conditioning that brought down the Roman Empire. With air conditioning their windows were shut, they couldn’t hear the barbarians coming. -- Garrison Keillor -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFHnUZNBkIOoMqOI14RAvPfAJ9gBxtJxjfGemlOl+4EllY61WyyZQCfTcC9 /7s+ttnYhH7uk3ahlkjXb1s= =PJjD -END PGP SIGNATURE-
Re: Leopard Migration Hammered Mutt
On Sun, Jan 27, 2008 at 08:49:04PM CST, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: From: Peter Münster [EMAIL PROTECTED] On Sat, Jan 26 2008, [EMAIL PROTECTED] wrote: PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin Mutt is in /sw/bin/ How can I add /sw/bin/ to my path? Just after logging in, you can enter the command ls -alrut, that shows in the last lines, the files that have just been read. Among these files, there should be an initialisation file for your shell, for example .bashrc or .profile. In the end of this file, you can put the line PATH=$PATH:/sw/bin Your suggestion below pointed out that .bash_profile is the initialization file. But .bash_profile has no references to Path in it. I can add PATH=$PATH:/sw/bin as you suggested, but will adding this override my original Path variable, or simply add it to the existing path? Your ~/.bash_profile doesn't need any initial references to PATH, because your shell inherits the default value from its parent process. Without creating ~/.bash_profile, open a Terminal.app window and type echo $PATH to see the shell's default value. Going this way, I would go with Peter Münster's suggestion. If it is possible I would rather add /sw/bin to the resource file where the rest of my Path is stored. How would I go about doing this? /sw indicates Fink. http://www.finkproject.org/doc/bundled/install-fast.php The last command runs a little script to help set up your Unix paths (and other things) for use with Fink. In most cases, it will run automatically, and prompt you for permission to make changes. If the script fails, you'll have to do things by hand. (If you need to do things by hand, and you are using csh or tcsh, you need to make sure that the command source /sw/bin/init.csh is executed during startup of your shell, either by .login, .cshrc, .tcshrc, or something else appropriate. If you are using bash or similar shells, the command you need is . /sw/bin/init.sh, and places where it might get executed include .bashrc and .profile.) So basically add the line . /sw/bin/init.sh into your ~/.profile or ~/.bash_profile init files. This should add /sw/bin to your PATH, and set up other Fink-related environment variables as well. -- Eugene
Re: Leopard Migration Hammered Mutt
Thanks for the thorough explanation. It helped me to grasp how the whole Path
thing works.
Since I would like to add /sw/bin to my /etc/profile I opened it, but only
discovered:
___
# System-wide .profile for sh(1)
if [ -x /usr/libexec/path_helper ]; then
eval `/usr/libexec/path_helper -s`
fi
if [ ${BASH-no} != no ]; then
[ -r /etc/bashrc ] . /etc/bashrc
fi
___
This is not what I expected, and can't think of where I should add /sw/bin/
to my path.
I appreciate your patience.
Bill
-- Original message --
From: Kyle Wheeler [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, January 28 at 02:49 AM, quoth [EMAIL PROTECTED]:
Your suggestion below pointed out that .bash_profile is the
initialization file. But .bash_profile has no references to Path
in it. I can add PATH=$PATH:/sw/bin as you suggested, but will
adding this override my original Path variable, or simply add it to
the existing path?
It adds it to the existing path.
Your Path is stored as a colon-separated list of folders containing
programs (e.g. /bin:/usr/bin:/sbin:/usr/sbin). The string $PATH is
a reference to the existing path---if you say echo $PATH your shell
will print out your current PATH, because that's the string referred
to be the notation $PATH. When you tell your shell to set a variable
name to be something, it performs a similar kind of expansion. For
example, if you say FOO=$PATH, the variable FOO will now contain a
copy of the contents of the variable $PATH. You can append things to
variable expansions, because the shell operates almost entirely in
terms of lines of text. For example, if you say FOO=word, then the
command echo $FOO will print out word. If you then say
BAR=$FOO-plunkity, the BAR variable will consist of word-plunkity. A
similar think would happen had you instead said FOO=$FOO-plunkity,
which is that FOO would then be a reference to the text
word-plunkity. Do you see how that works?
Thus, the command suggested, PATH=$PATH:/sw/bin, will set the PATH
to be a string consisting of whatever $PATH is (i.e. your current
path), a colon, and the string /sw/bin. It will not throw away your
existing path.
If it is possible I would rather add /sw/bin to the resource file
where the rest of my Path is stored. How would I go about doing
this?
That would be /etc/profile
~Kyle
- --
It was luxuries like air conditioning that brought down the Roman
Empire. With air conditioning their windows were shut, they couldnât
hear the barbarians coming.
-- Garrison Keillor
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!
iD8DBQFHnUZNBkIOoMqOI14RAvPfAJ9gBxtJxjfGemlOl+4EllY61WyyZQCfTcC9
/7s+ttnYhH7uk3ahlkjXb1s=
=PJjD
-END PGP SIGNATURE-
Re: Leopard Migration Hammered Mutt
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday, January 28 at 03:31 AM, quoth [EMAIL PROTECTED]: Thanks for the thorough explanation. It helped me to grasp how the whole Path thing works. Since I would like to add /sw/bin to my /etc/profile I opened it, but only discovered: ___ # System-wide .profile for sh(1) if [ -x /usr/libexec/path_helper ]; then eval `/usr/libexec/path_helper -s` fi Hmmm. I don't have path_helper (I still use Tiger), but I'm willing to bet that it's got some hard-coded method of guessing your path. You have two options: either investigate path_helper and see what it's doing, or resign yourself to adding /sw/bin to your path in your own home directory. ~Kyle - -- Genius may have its limitations but stupidity is not thus handicapped. -- Elbert Hubbard -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFHnU7nBkIOoMqOI14RAviaAJ9YXQhzhDGqemQltboU3QEXZ4xP0QCg737a l5bRPYgS97t6v7NtHnqGVww= =M022 -END PGP SIGNATURE-
Re: Leopard Migration Hammered Mutt
* Eugene [EMAIL PROTECTED] [2008-01-27 21:18 -0600]: So basically add the line . /sw/bin/init.sh into your ~/.profile or ~/.bash_profile init files. This should add /sw/bin to your PATH, and set up other Fink-related environment variables as well. All the explanations have been helpful. The only thing I'd add is an explanation that the line . /sw/bin/init.sh is a shortcut telling the shell to execute the script /sw/bin/init.sh (which has to have execute permission). The shell commands in init.sh get executed and change your path. The leading '.' is easy to miss, but it's a common usage in shell scripts. Breen -- Breen Mullins Menlo Park, California
Re: Leopard Migration Hammered Mutt
Here's what I was able to come up with about path_helper: ___ In Leopard, Apple has introduced a new mechanism for managing and maintaining your system path ($PATH). Previously (and in most current Linux environments) paths were managed by updating the PATH environment variable directly in either the system profile (/etc/profile) or your local profile (~/.bash_profile). Commonly you had entries like: export JAVA_HOME = /usr/lib/j2se/jdk1.5.0_13/ export PATH=$PATH:$JAVA_HOME/bin ... In Leopard, you no longer have to modify the profile to make adjustments to system paths. Instead, you can put a simple text file containing a path entry (or entries) into /etc/paths.d/. Each line in this file will be interpreted as a path and added automatically to the system path. littlesquare.com ___ Thanks for everyone's patient assistance. Bill -- Original message -- From: Kyle Wheeler [EMAIL PROTECTED] -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday, January 28 at 03:31 AM, quoth [EMAIL PROTECTED]: Thanks for the thorough explanation. It helped me to grasp how the whole Path thing works. Since I would like to add /sw/bin to my /etc/profile I opened it, but only discovered: ___ # System-wide .profile for sh(1) if [ -x /usr/libexec/path_helper ]; then eval `/usr/libexec/path_helper -s` fi Hmmm. I don't have path_helper (I still use Tiger), but I'm willing to bet that it's got some hard-coded method of guessing your path. You have two options: either investigate path_helper and see what it's doing, or resign yourself to adding /sw/bin to your path in your own home directory. ~Kyle - -- Genius may have its limitations but stupidity is not thus handicapped. -- Elbert Hubbard -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFHnU7nBkIOoMqOI14RAviaAJ9YXQhzhDGqemQltboU3QEXZ4xP0QCg737a l5bRPYgS97t6v7NtHnqGVww= =M022 -END PGP SIGNATURE-
