Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comparing alot vs other Notmuch-based MUAs, including mutt-kz #776

Closed
johnnyutahh opened this issue Jul 12, 2015 · 8 comments
Closed

Comparing alot vs other Notmuch-based MUAs, including mutt-kz #776

johnnyutahh opened this issue Jul 12, 2015 · 8 comments
Labels

Comments

@johnnyutahh
Copy link

Can the alot community comment on my initial comparisons with other Notmuch-based MUAs, namely mutt-kz?

https://github.com/johnnyutahh/search-based-email#MUA_choice

I haven't revisited the alot resources (github, software, etc) since April/May 2015 timeframe, so if there's been significant changes since, I've not seem them.

Feedback on the rest of my questions in the above document are welcome.

@pazz pazz added the doc label Jul 13, 2015
@pazz
Copy link
Owner

pazz commented Jul 13, 2015

Hi and welcome to alot!
I think you're right that an example config could help newcommers.
I am a little surprized to hear about alot's "sparse" documentation compared to muttrc.
Does muttrc have more than a RADME? Are you aware of alot.rtfd.org?
You might find the config section useful.. Have fun,
/p

@johnnyutahh
Copy link
Author

Hi Patrick,

Thanks for the welcome. mutt and mutt-kz have several rich, diverse, and
example-config references. Here's some of the better ones I've found
thus far:

https://github.com/johnnyutahh/search-based-email#mutt-kz-applicable-configuration

And yes, I am (and was) familiar with alot.rtfd.org, including the
config section. However, the easiest uptake for a user like me is to
provide examples, workflows, user scenarios, etc--things like above--and
then read the "reference manual" like alot.rtfd.org (currently) to
figure out any details I couldn't figure out from the examples,
workflow, scenario docs.

Here's an analogy: it's hard to build a house with just carpentry tools
like a hammer and saw (unless I've previously built the same or similar
house). It's much easier if I can see a blueprint, design, and/or
example of another house. My experience (which frankly might be just
wrong--I'm still learning and investigating) is that alot.rtfd.org
provides the carpentry tools, but I have no other examples, or designs,
or recommendations like I'd get from a blueprint or an example house. I
have to figure out all the latter by myself. And that's much harder. And
currently an impediment for me trying to master alot.

Is this possibly an unfair analogy? Sure. But for better or worse, it's
my current experience. I'd be very happy to discover stuff I've not yet
seen, and/or get a better understanding of alot.rtfd.com or other,
existing docs.

Amplifying the above problem is that, while I do have programming and
cmdline-usage, and "text-y" skills and experience, I haven't employed
these kinds of programming/cmdline/text-y approaches (at least, not
recently) to MUAs/email usage. So I might be learning much more than
just 'alot'. And because of all this, alot feels like too daunting a
learning curve. My current plan is to start trying/using mutt-kz, and
then maybe try alot later. Do you have any alternative suggestions?

More on my usage background, requirements, and cmdline-based-email
learning challenges here:
https://github.com/johnnyutahh/search-based-email

Does this all make sense?

On 7/13/15, 5:46 PM, Patrick Totzke wrote:

Hi and welcome to alot!
I think you're right that an example config could help newcommers.
I am a little surprized to hear about alot's "sparse" documentation
compared to muttrc.
Does muttrc have more than a RADME? Are you aware of alot.rtfd.org?
You might find the config section
http://alot.readthedocs.org/en/latest/configuration/index.html
useful.. Have fun,
/p


Reply to this email directly or view it on GitHub
#776 (comment).

@pazz
Copy link
Owner

pazz commented Jul 15, 2015

Hi again,
I did not use mutt for too long until I wrote alot, so I cannot really compare them in terms of user friendliness. At the time, muttkz was not available and when I tried it, I had a hard time getting into it.
Anyhow, good luck with muttkz. If you do try alot later, I welcome you to write about the exact
problems you run into etc. It's always good to improve upon the docs :)

@geier
Copy link
Collaborator

geier commented Jul 15, 2015

@johnnyutahh I believe alot is not that hard to get into. If you don't know the commands yet press ? for a scrollable list of commands (while in alot). Until I found someone's alot config a messed up when trying to write my own config, especially with the bindings. If you need a simpler example, you might want to have a look at mine and e.g. offlineimaprc for the post sync workflow.

But looking through pazz config I realise I'm currently missing out on some nice automation possibilities.

@pazz
Copy link
Owner

pazz commented Jul 16, 2015

Quoting Christian Geier (2015-07-15 20:38:38)

But looking through pazz config I realise I'm currently missing out on
some nice automation possibilities.

FTR: my config on github was way outdated. I pushed my current config if you
want to have a peek. It is full of commented out stuff that was introduced
to test features i'm not using myself :)

@geier
Copy link
Collaborator

geier commented Jul 16, 2015

@pazz thank you! especially for hooks.github()

@johnnyutahh
Copy link
Author

@geier @pazz -- all helpful feedback, thank you.

@pazz: is this the config mentioned above?
https://github.com/pazz/configs/blob/master/.config/alot/config

@lucc
Copy link
Collaborator

lucc commented Aug 9, 2017

I will close this. If there are more specific ideas how to improve the docs you can open a new PR.

@lucc lucc closed this as completed Aug 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants