emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dan Davison <davison@stats.ox.ac.uk>
To: Benjamin Andresen <benny@in-ulm.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org-FAQ request for full-text dump
Date: Thu, 13 May 2010 00:13:57 -0400	[thread overview]
Message-ID: <87ocgk781m.fsf@stats.ox.ac.uk> (raw)
In-Reply-To: <87632swrjt.fsf@in-ulm.de> (Benjamin Andresen's message of "Thu, 13 May 2010 02:53:26 +0200")

Benjamin Andresen <benny@in-ulm.de> writes:

> Hello guys,
>
> quite often people ask question in the IRC-channel (#org-mode on
> freenode) which are answered in the FAQ. Now I personally find the
> org-faq very cumbersome to use, due to its javascript-interface that
> grabs keys.

+1

The info.js HTML export is an excellent invention, but I don't think
it's right for the FAQ, at least not with the current setup. Personally
I sometimes skim FAQs to get a sense of a project, and I think visitors
should be able to scroll down / search in a familiar fashion to get more
information. I think obliging random web visitors to use Info style
navigation by default is a bad idea. To be honest I've never read
anything in the FAQ because I can't easily skim it, and if I have a
specific question I look in the manual.

In addition to a flat format, a possible better way to use info.js for
the FAQ would be in a "startup contents" mode, whereby all headings and
questions are visible, but question answers are not.

Dan

>
> (Just a short thing: I'm faster with my native browser search
> functionality than with the interface that is used on org-faq.php
>
> In my browser it's: /color n n n N n
>
> vs.
>
> s color s RET s RET s RET and I don't even know how to jump back to a
> previous search results (also sometimes the first search doesn't even
> work, I have to do it twice, haven't investigated this further.))
>
> Because of this I currently use the org-faq.org file locally and
> then grab the CUSTOM_ID and attach it to the org-faq.php link as an
> anchor.
>
> So my question is basically: Could we get a plain dump of the file?
>
> (I don't know who controls the export and I guess just copying the file
> and stripping out all the infoJS stuff is not the right way to do it.)
>
> br,
> benny
>
> Please don't take offense, I'm sure many other people like the infoJS
> interface, I just find it inefficient and mainly different from the way
> I search the web.
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2010-05-13  4:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-13  0:53 Org-FAQ request for full-text dump Benjamin Andresen
2010-05-13  4:13 ` Dan Davison [this message]
2010-05-13 16:46   ` Include FAQ to info? (was: Org-FAQ request for full-text dump) Memnon Anon
2010-05-15  6:46     ` Carsten Dominik
2010-05-15 19:01       ` Matt Lundin
2010-05-16  6:45         ` Carsten Dominik
2010-05-16 12:43           ` Matthew Lundin
2010-05-21 21:01             ` Alan E. Davis
2010-05-22 16:32               ` Include FAQ to info? Matthew Lundin
2010-05-15  6:54   ` Re: Org-FAQ request for full-text dump Carsten Dominik
2010-05-13 11:13 ` Sebastian Rose

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ocgk781m.fsf@stats.ox.ac.uk \
    --to=davison@stats.ox.ac.uk \
    --cc=benny@in-ulm.de \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).