You are not logged in.
I have configured mutt for my two imap account as stated in the wiki (with F2 macro for the main account and F3 macro for the other account).
I'm wondering if there's any way to merge them in one view only (like in thunderbird) in order to see them with one glance, update them at once and check in an istant if there's new mail...
And if in mutt there's no way to do this, is there any console application that can do that? Or can I open mutt in two terminals specifing which inbox to check in which istance?
Last edited by Delcaran (2013-07-01 16:43:52)
I apologize for my English...
Offline
I have configured mutt for my two imap account as stated in the wiki (with F2 macro for the main account and F3 macro for the other account).
I'm wondering if there's any way to merge them in one view only (like in thunderbird) in order to see them with one glance, update them at once and check in an istant if there's new mail...And if in mutt there's no way to do this, is there any console application that can do that? Or can I open mutt in two terminals specifing which inbox to check in which istance?
I don't know about merging in mutt, as I don't use imap, but mutt was designed to have multiple running instances - even on the same account, it's possible.
I have two running instances, one for work and one for personal email folders. I specify a different mutt config file for each.
All sections of the config file are split and I source the different sections. That way I can have one file or common settings (colours, key mappings, macros, etc.) and separate ones where necessary (account settings, paths, etc.).
See the "source" command in the config file.
Last edited by skanky (2013-07-01 16:34:53)
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle
Offline
All sections of the config file are split and I source the different sections. That way I can have one file or common settings (colours, key mappings, macros, etc.) and separate ones where necessary (account settings, paths, etc.).
I see... one file per account, both sourcing the common configuration files... I think that's the right way!
I apologize for my English...
Offline
Yep, it works! Now I need to configure i3wm to load them in the corret workspace in the correct layout togheter with newsbeuter ![]()
I apologize for my English...
Offline
Yep, it works! Now I need to configure i3wm to load them in the corret workspace in the correct layout togheter with newsbeuter
Cool.
Just for reference, this is the up to date manual (I think it's a bit harder to find than the older one): http://dev.mutt.org/doc/manual.html
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle
Offline
Yep, it works! Now I need to configure i3wm to load them in the corret workspace in the correct layout togheter with newsbeuter
I use i3 & have many windows/apps open on different workspaces, here is the syntax I use in i3 config:
assign [title=".::MUTT::."] 2I use "title" because mutt uses terminator thus:
exec terminator -p mutt --title .::MUTT::.-p mutt tells terminator to use profile mutt which is what executes the mutt binary
--title .::MUTT::. is what tells terminator to use as the window name:
WM_ICON_NAME(STRING) = ".::MUTT::."for reference use:
http://i3wm.org/docs/userguide.html#command_criteria
along with:
xprop | grep WM_to work out what you need to use.
One gotcha I found out was that if anywhere in your i3 workspaces assignments you use:
assign [class="terminator"] 5this will override all other assignments for terminator windows which will result in them all opening on the workspace as stated in the class assignment.
here is my i3 config if you want to take some parts of it for yours
http://bpaste.net/show/111121/
Last edited by t0m5k1 (2013-07-02 07:18:10)
Offline
I use "title" because mutt uses terminator thus:
Maybe it would be better to use window_role or class since terminator allows you to set WM_WINDOW_ROLE and WM_CLASS. I think it is very unlikely that mutt changes the title before i3 assigns the workspace but it might still be possible.
Last edited by progandy (2013-07-02 07:16:26)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |
Offline
t0m5k1 wrote:I use "title" because mutt uses terminator thus:
Maybe it would be better to use window_role or class since terminator allows you to set WM_WINDOW_ROLE and WM_CLASS. I think it is very unlikely that mutt changes the title before i3 assigns the workspace but it might still be possible.
as soon as you use role or class an other i3 workspace assignments will be ignored!
mutt does not change the name, my gotcha refers to i3 giving precedence to class & role over the other WM_ elements that is all
So if you want a main terminal open on 1 workspace & others of the same terminal placed on another workspace then you cannot use class or role.
I know this through day's of headache trying to work out why
Last edited by t0m5k1 (2013-07-02 07:25:11)
Offline