From: Daniel Clemente <n142857@gmail.com>
To: Brady Trainor <algebrat@uw.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-mode for knowledge management
Date: Sun, 12 Oct 2014 11:29:52 +0700 [thread overview]
Message-ID: <87mw91hpvj.wl-n142857@gmail.com> (raw)
In-Reply-To: <87wq86crva.fsf@uw.edu>
El Sat, 11 Oct 2014 12:45:45 -0700 Brady Trainor va escriure:
>
> > About links: in org-mode they all look the same, but semantically there are many types, like:
> > […]
> > - *same-as*: „this and [[that]] are exactly the same topic, so write
> > only under that header, not here“
> > […]
> I don't think I am aware of the "*sameas*" type of link in org-mode, can
> you give an example please?
>
There's only 1 type of link between headers in org-mode; what's different is the way in which you use it.
* About web pages
** CSS
** HTML
*** Convert to other formats
**** convert to JSON
Use html2json
**** convert to PDF → see [[html_to_pdf]]
* About PDFs
** create them
*** from .odt
Click that icon.
*** from .html. id:html_to_pdf
There's this method…
*** from .tex
In this case, that „HTML→PDF“ section could live under the „web pages“ tree or under the „PDFs“ tree, and there's no difference because it's exactly the same information.
If you consider „link following“ as a trivial operation, you could say that that knowledge is accessible under both trees at the same time. It's not transclusion, but it works the same.
Note that in the example above, the „→ see …“ header must be empty of content. If you write inside, it's not a light link anymore, it's a header on its own.
Org-mode could offer this type of header built-in (a light header is a header which must link to another one and have no content), but you can do it with the current tools and a bit of care.
next prev parent reply other threads:[~2014-10-12 4:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-09 22:17 org-mode for knowledge management Louis
2014-10-09 23:54 ` Marcin Borkowski
2014-10-10 15:46 ` Daniel Clemente
2014-10-10 21:40 ` mbork
2014-10-10 21:48 ` John Hendy
2014-10-11 2:53 ` Eric Abrahamsen
2014-10-12 4:54 ` John Hendy
2014-10-13 2:42 ` Eric Abrahamsen
2014-10-13 3:15 ` Daniel Clemente
2014-10-13 5:17 ` Samuel Wales
2014-10-14 3:47 ` Daniel Clemente
2014-10-14 1:14 ` Eric Abrahamsen
2014-10-11 11:36 ` Daniel Clemente
2014-10-11 19:45 ` Brady Trainor
2014-10-12 4:29 ` Daniel Clemente [this message]
2014-10-12 5:03 ` John Hendy
2014-10-12 7:48 ` Daniel Clemente
2014-10-14 2:14 ` John Hendy
2014-10-10 0:18 ` Thomas S. Dye
2014-10-10 2:32 ` Louis
2014-10-10 2:34 ` Louis
2014-10-13 19:29 ` Louis
2014-10-13 19:36 ` Thomas S. Dye
2014-10-13 23:10 ` Louis
2014-10-13 13:11 ` Brett Viren
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=87mw91hpvj.wl-n142857@gmail.com \
--to=n142857@gmail.com \
--cc=algebrat@uw.edu \
--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).