From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Feature request: info-org-manual
Date: Sat, 28 Sep 2013 12:34:02 +0200 [thread overview]
Message-ID: <20130928103402.GP12411@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <20130928122405.7ed5cbfa@aga-netbook>
On Sat, Sep 28, 2013 at 12:24:05PM +0200, Marcin Borkowski wrote:
> Dnia 2013-09-28, o godz. 12:16:52
> Carsten Dominik <carsten.dominik@gmail.com> napisał(a):
>
> >
> > On 28.9.2013, at 12:10, Suvayu Ali <fatkasuvayu+linux@gmail.com>
> > wrote:
> >
> > > Hi Marcin,
> > >
> > > On Sat, Sep 28, 2013 at 11:53:30AM +0200, Marcin Borkowski wrote:
> > >> Hi,
> > >>
> > >> there is the info-emacs-manual, bound to C-h r. Why not introduce
> > >> info-org-manual, like this:
> > >
> > > I'll play the Devil's advocate, there are many emacs packages with
> > > info pages of their own. AFAIK, none of them do this. That said,
> > > if such a command is introduced, probably it should be org-info;
> >
> > That command does already exist. Also accessible from
> > the Org menu, under Documentation. And indeed, we need to stay
> > in org's namespace, I agree.
>
> Sorry, then. It happened once again: I thought "it would be nice if
> Org had such-and-such feature", and it already has it... It's kinda
> creepy;). (I'll probably bind it to some handy key in my init.el,
> though.)
Yeah, happens all the time. I have been using Org since 2009 I think,
and I didn't know!
:)
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2013-09-28 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-28 9:53 Feature request: info-org-manual Marcin Borkowski
2013-09-28 10:10 ` Suvayu Ali
2013-09-28 10:16 ` Carsten Dominik
2013-09-28 10:24 ` Marcin Borkowski
2013-09-28 10:34 ` Suvayu Ali [this message]
2013-09-28 10:43 ` Marcin Borkowski
2013-09-29 11:56 ` Memnon Anon
2013-09-28 11:44 ` Nicolas Richard
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=20130928103402.GP12411@kuru.dyndns-at-home.com \
--to=fatkasuvayu+linux@gmail.com \
--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).