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

write documentation #23

teythoon opened this issue Dec 24, 2011 · 9 comments

write documentation #23

teythoon opened this issue Dec 24, 2011 · 9 comments


Copy link

@teythoon teythoon commented Dec 24, 2011

No description provided.

@ghost ghost assigned teythoon Dec 24, 2011
Copy link

@nickurak nickurak commented Jan 22, 2012

It seems like the basic instructions in the README are pretty good. What I think would be most helpful would be some more examples, and some discussion of what afew is good at, and what it's not.


  • How to set up spam auto-tagging
  • How to set up mailing-list auto-tagging
Copy link

@stapelberg stapelberg commented Apr 15, 2012

I disagree with "the instructions in the README are pretty good".

Take for example:

Basic tagging stuff requires no configuration, just run
$ afew --tag --new

What exactly is "basic tagging stuff"? I have no idea what that means. Why would I even run that command? notmuch automatically adds a tag for new messages. What exactly does afew do different? Or on top of that? I don’t know.

Also, based on reading the user manual, it seems that there is a default spamfilter. How can I turn that off? I already have spam filtering in a different place in my mail infrastructure.

Copy link
Collaborator Author

@teythoon teythoon commented Apr 16, 2012

@mstap: Agreed, the current documentation is not sufficient, especially for new users.

Copy link

@amandasystems amandasystems commented Jul 7, 2012

I agree. What I'd like to see is primarily how to define your own filters, which I (after several hours of frantic googling) still don't think I've quite figured out.

Copy link

@ghost ghost commented Jul 17, 2013

What documentation is needed? It would be helpful to have issues for the different places that need more documentation.

Copy link

@lucc lucc commented Apr 6, 2016

Any news on this? What can people besides @teythoon do to work on this issue?

Copy link

@ghost ghost commented Apr 6, 2016

No one.

@flokli flokli removed this from the release 1.1 milestone Jun 19, 2017
Copy link

@pohly pohly commented Apr 10, 2018

I found afew via which directly links to the repo. Then I was struggling to understand the main README.rst because (as discussed in this issue) it left some open questions.

But then I found the more extensive documentation in the docs folder respectively at and that was good enough.

I suggest to shorten the main README.rst so that it doesn't duplicate information from the full documentation (basically just leaving a summary and a link) and then close this issue. Agreed? I can prepare a PR.

Copy link

@flokli flokli commented Apr 10, 2018

@pohly yes, sounds good, thanks :-)

pohly added a commit to pohly/afew that referenced this issue Apr 11, 2018
The instructions in README.rst duplicated some of the information in
the more complete docs, but not enough to really get started using
afew. It is better to avoid duplication and refer new users directly
to the full documentation.

The README.rst installation instructions were slightly more complete
and recent, so they were copied to the

While at it, fix broken links in the rst markup.

Fixes: afewmail/afew/afewmail#23.
@flokli flokli closed this in #191 Apr 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

7 participants