emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Sebastian Rose <sebastian_rose@gmx.de>
Cc: emacs-orgmode@gnu.org,
	Nathaniel Cunningham <nathaniel.cunningham@gmail.com>
Subject: Re: searchable refcard?
Date: Tue, 2 Dec 2008 09:33:01 +0100	[thread overview]
Message-ID: <AD189794-66D9-4CE0-861B-2500CF207963@gmail.com> (raw)
In-Reply-To: <874p1o6juq.fsf@kassiopeya.MSHEIMNETZ>

Hi Sebastian,

On Dec 1, 2008, at 3:38 PM, Sebastian Rose wrote:

> Hi Carsten, Alan & Co,
>
>
> sorry for not following this thread closely. If the idea here is  
> deleted
> from your list already or is not feasable, just ignore it.
>
>
>
> Refcard as info file
> ====================
>
>  How about maintaining the extended refcard as a second texinfo file?
>  After the install, we would have two resulting info files: org and
>  org-refcard.
>
>  We could then bind a key to some `org-open-ref-card' function, that
>  simply calls (info "(orgrefcard)").


If this would be done in info format (i.e. TexInfo), then it could
simply be part of the manual itself and info could jumpt to that
particular node in the manual.

>
>
>
>
> Context help
> ============
>
>  As for help in general:
>
>  How about binding a key (e.g. `C-c h') to a function calling (info
>  &optional file-or-node) to get context-help while in an org-file?
>
>  (info "(org)tags")                      if on a tag,
>  (info "(org)properties and columns")    if in `#+COLUMNS' line
>
>  ...and so on.
>
>  Often more than one section will match, so a mapping would be needed
>  as well, as some sort of completion.

I do like that idea.

- Carsten

  reply	other threads:[~2008-12-02  8:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-27  1:21 searchable refcard? Nathaniel Cunningham
2008-11-27 10:07 ` Sebastian Rose
2008-11-27 12:17   ` Alan E. Davis
2008-11-27 15:55     ` Carsten Dominik
2008-11-28  2:44       ` Alan E. Davis
2008-11-30  8:54         ` Carsten Dominik
2008-12-01 12:56           ` Alan E. Davis
2008-12-01 13:06             ` Carsten Dominik
2008-12-01 14:38               ` Sebastian Rose
2008-12-02  8:33                 ` Carsten Dominik [this message]
2008-12-02 12:28                   ` Sebastian Rose
2008-12-02 13:01                     ` Carsten Dominik
2008-12-02 14:35                       ` Sebastian Rose
2008-11-28  7:06   ` Nathaniel Cunningham
2008-12-03 20:40     ` Samuel Wales
2008-12-04  8:10       ` Carsten Dominik
2008-12-11  3:42         ` Samuel Wales

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=AD189794-66D9-4CE0-861B-2500CF207963@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=nathaniel.cunningham@gmail.com \
    --cc=sebastian_rose@gmx.de \
    /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).