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

Update user documentation #488

Closed
xiaq opened this issue Jan 1, 2013 · 12 comments
Closed

Update user documentation #488

xiaq opened this issue Jan 1, 2013 · 12 comments
Labels
docs An issue/PR that touches or should touch the docs

Comments

@xiaq
Copy link
Contributor

xiaq commented Jan 1, 2013

http://ridiculousfish.com/shell/user_doc/html/ is badly outdated. The footer says: Generated on Fri May 25 02:21:14 2012 for fish by doxygen 1.5.9

@ridiculousfish Perhaps write a script to update the user doc automatically :)

@siteshwar
Copy link
Contributor

Also I think whole documentation needs to be reviewed and updated before Fish 2.0 release as it may be lagging behind.

@ridiculousfish
Copy link
Member

The ridiculousfish.com documentation is for the beta, and I will close that site down when we release.

When we release fish 2.0, the site will be fishshell.com, and the online documentation will live at http://fishshell.com/docs/2.0/index.html . In fact it's already there, and should be up to date.

@siteshwar
Copy link
Contributor

I noticed a few issues in the documentation. Here are the improvements I would like to see :

  1. Add description of how auto suggestions work.
  2. Update how completions work : http://fishshell.com/docs/2.0/index.html#completion
  3. Update the design philosophy page. We break design laws at some places. For e.g. We have implemented our own version of echo for performance reasons which breaks law of minimalism. - http://fishshell.com/docs/2.0/design.html
  4. Add GitHub fish-shell issues link in "Missing features and bugs" section. - http://fishshell.com/docs/2.0/index.html#todo
  5. Add address of our IRC channel and mailing list in FAQs http://fishshell.com/docs/2.0/faq.html
  6. Remove obsolete FAQs like http://fishshell.com/docs/2.0/faq.html#faq-cd-implicit

@siteshwar
Copy link
Contributor

Also we need to add docs for printf builtin in Fish. Since we have derived printf from GNU Coreutils, we can just refer to http://www.gnu.org/software/coreutils/manual/html_node/printf-invocation.html

@siteshwar
Copy link
Contributor

Added docs for printf in 516be01

@zanchey
Copy link
Member

zanchey commented Jun 4, 2013

Outstanding issues from this list:

@mrshu
Copy link
Contributor

mrshu commented Aug 19, 2013

@zanchey what is the state of this? Can I be of any help?

I see that there is a section on auto suggestions in tutorial, is that what you had in mind with this?

@zanchey
Copy link
Member

zanchey commented Aug 20, 2013

I've made a separate issue to remind me about autosuggestions (#937). Any updates to the documentation are always welcome; completions might be a good place to start.

@davidxia
Copy link
Contributor

@zanchey @siteshwar Is there still work to be done? Can I help out?

@zanchey
Copy link
Member

zanchey commented Jul 8, 2014

I actually had a grand plan to rewrite large swathes of the non-reference part of the documentation, but it hasn't really happened yet. Any work improving the accuracy, completeness or readability of the documentation would be greatly appreciated.

@davidxia
Copy link
Contributor

davidxia commented Jul 8, 2014

Any parts in particular?

@faho
Copy link
Member

faho commented Jan 16, 2016

The docs at http://fishshell.com/docs/current/index.html document the latest release, so there's nothing to do here ("improve documentation" is pretty much an ongoing task that can just stay implicit).

@faho faho closed this as completed Jan 16, 2016
@faho faho removed this from the next-major milestone Jan 16, 2016
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 18, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
docs An issue/PR that touches or should touch the docs
Projects
None yet
Development

No branches or pull requests

7 participants