Hooks and user's own macros? about astroid HOT 22 CLOSED

from astroid.

Well, I wouldn't need anything fancy and so using shell for notmuch commands would make me very happy :-) / for instance:

thread_index.hook(notmuch tag -inbox -unread +archive)=a

from astroid.

Hugo Roy writes on January 3, 2016 21:36:

Well, I wouldn't need anything fancy and so using shell for notmuch commands would make me very happy :-) / for instance:

thread_index.hook(notmuch tag -inbox -unread +archive)=a

Yeah, this seems like a good idea, but perhaps use something like:

main_window.run
thread_index.run
thread_index.multi.run

with pre-defined arguments.

from astroid.

I don't know. That looks like another configuration file needed to pre-define the arguments. I think it's alright if it's not pre-defined. But I don't have strong arguments any way.

from astroid.

What I mean is that you can configure e.g.:

thread_index.run(notmuch tag -inbox -unread +archive)=a

which will run the command with one argument which is the thread id of
the currently selected thread:

notmuch tag -inbox -unread +archive thread:00000xxx

but you could also use your own script:

thread_index.run(~/.config/astroid/scripts/toggle_archive)=a

where you use notmuch commands to check if it already is archived and
then do what you want.

so the command:
thread_index.run will be run with 'thread:0000xxx' as the first and only
argument.

thread_index.multi.run will run the command with one argument for each
thread so that the script that gets it can act on all of them.

In this way you can:

• create a script to toggle archive
• output the file (using notmuch commands) or do something with it, as in #36 (probably fixing that issue?)

you do not need another configuration file.

from astroid.

↪ janvier 4, 2016 10:18 , Gaute Hope:

What I mean is that you can configure e.g.:

thread_index.run(notmuch tag -inbox -unread +archive)=a

which will run the command with one argument which is the thread id of
the currently selected thread:

notmuch tag -inbox -unread +archive thread:00000xxx

but you could also use your own script:

thread_index.run(~/.config/astroid/scripts/toggle_archive)=a

where you use notmuch commands to check if it already is archived and
then do what you want.

Okay, now I understand. Yes this is pretty much perfect I think :)

In this way you can:

• create a script to toggle archive
• output the file (using notmuch commands) or do something with it, as in #36 (probably fixing that issue?)

Yes, that looks like a very, very good start to enable this indeed.

from astroid.

Once the parser for this is up I think the following commands
should also be supported:

(mode here is either 'main_window' (which works for all),
'thread_index', etc).

mode.search('query:asdfasdf')=keyspec
thread_index.toggle_tag('tag_a,tag_b')=keyspec
thread_view.toggle_tag('tag_a,tag_b')=keyspec

from astroid.

Fixed in #76.

from astroid.

@gauteh any idea how to use something like

thread_index.run(/home/hugo/.config/astroid/hooks/toggle waiting %1)=w

on an email in thread_view rather than on an whole thread?

from astroid.

from astroid.

from astroid.

from astroid.

I've added an example in the wiki for thread_view.run using %2 as message ID

from astroid.

from astroid.

from astroid.

from astroid.

@hugoroy is this something where my wiki additions have been unclear, or just a random mistake?

from astroid.

from astroid.

from astroid.

from astroid.

Done. But there's room for optimization I guess :)

Thanks! One question: shouldn't the second example have thread_view.run as keybinding?

from astroid.

from astroid.