Brady Trainor algeb...@uw.edu writes:
synopsis: want (clickable) customize to open in a new frame
Fiddling with the following variable may help (NB: untested,
and no time to dig, so I may be leading you up the garden path):
,
| org-link-frame-setup is a variable defined in `org.el'.
|
Nick Dokos ndokos at gmail.com writes:
Brady Trainor algebrat at uw.edu writes:
synopsis: want (clickable) customize to open in a new frame
Fiddling with the following variable may help (NB: untested,
and no time to dig, so I may be leading you up the garden path):
,
Brady Trainor algebrat at uw.edu writes:
[...] I think I'll Pandoc the manual into org to practice the manual's
navigation.
Converting the html version to org met with some difficulties, such as
carriage returns and pandoc giving an overflow.
Should probably just get
Brady Trainor algeb...@uw.edu writes:
Brady Trainor algebrat at uw.edu writes:
...
Should probably just get comfortable with the info version of elisp
manual.
Yes, you will be happiest when you are assimilated :-) Emacs insists on
info files for all packages distributed with it, so info is
Nick Dokos ndokos at gmail.com writes:
Yes, you will be happiest when you are assimilated
:borg:
Would be nice to have org versions of all info files.
[...] why do you
want to have org versions of all info files? What would the benefits
be?
[...] But rewriting
As I climb the org-mode (and Emacs) learning curve, I like to have things
like hyperlinks to frequently visited places available.
I can link to info, but not sure how to link to the customize, er, mode?
buffer?
I assume I should consider it an external link, or anyways assume I should
Nick Dokos ndokos at gmail.com writes:
Brady Trainor algebrat at uw.edu writes:
So, my naïve attempt is to use
elisp:customize
so to call it from an elisp link, you say
[[elisp:(customize)]]
Thank you for the speedy reply and solution!
Brady Trainor algeb...@uw.edu writes:
However, I am curious why I get away with
file:~/.emacs,
but not
elisp:(customize)
That is, I can get away with not using square brackets for the file, but we
need
[[elisp:(customize)]]
Not a priority, just a mild curiosity.
Actually, I
elisp:customize
should also work as a link, even without the brackets.
[...] so the question
is why it does not work for you.
It does work, I was wrong.
That is, `elisp:customize` does in fact work for me.
Not sure if I should start a new thread for the following.
---
