From: nielsgiesen@ibbu.nl
Cc: emacs-orgmode@gnu.org
Subject: Re: usage, ideas, suggestions, actually a braindumnp
Date: Thu, 27 Apr 2006 15:02:38 +0200 (CEST) [thread overview]
Message-ID: <20060427130238.92E602BDC@schimmel.ibbu.nl> (raw)
In-Reply-To: <50a334e65e65bbedf83c7db291aa484d@science.uva.nl> (message from Carsten Dominik on Thu, 27 Apr 2006 12:30:28 +0200)
On Apr 27, 2006, at 11:53, nielsgiesen@ibbu.nl wrote:
>> * Some other things that have come up during usage:
>> ** option for clean export view of timestamps
>
>Do you have an example of what you mean?
Timestamps without the angular brackets. Actually not that important,
although it might be nice in exporting tables, as applications using
this have their own ways of playing with such data. But then you'd
have to convert them back to the org-form when importing such a
table.
>> ** option to leave timestamps out in export function
>I guess, leave them out together with keywords like DEADLINE, SCHEDULED
>and CLOSED, right?
If they are grouped, yes.
>> ** option to leave tags out in export function.
>Useful, yes, or at least make them look better.
That was the idea behind the 'clean timestamps' too, though here it is
more important.
>> ** org-export-to-LaTeX
>Very unlikely that I will do this effort. Thought about it long ago
>and decided it was too much work for too little gain.
If time and use so merits, I will look into this myself.
>> ** make follow-mode the default as customization option;
>> for myself, I have just hacked the code to have follow-mode always on.
>Really, you want this always on? OK, I will make it an option. How
>did you hack it? You can of course use org-agenda-mode-hook to turn it
>on.
For lack of time to sniffing through the code and really understand it
to come up with an elegant solution, I simply put
(org-agenda-follow-mode t) near the end of each function called by C-c
a * (where * stands for each letter that I use at the moment).
>(add-hook 'org-agenda-mode-hook
> (lambda () (setq org-agenda-follow-mode t)
> (org-agenda-set-mode-name)))
Thanks, that's way better than my ugly hacks!
>> ** strip links when unexportable as link
>> Export description, or, when lacking, only the content of the link.
>Example where this goes wrong?
It is when you put a link inside a table, which is exported to csv and
just gives the raw ascii code in the exported table. Sorry for not
being clear enough.
Another one, where the link is valid, but just the layout not as
expected, is inside a headline to html, :
* DONE eerste bandje volledig begrijpen <<<1>>> DEADLINE: <2006-04-23
Sun>
exports as
<H2><a name="sec-1">1 <SPAN CLASS="DONE">DONE</SPAN> eerste bandje volledig begrijpen <<span class="target">1</span> > <SPAN CLASS="DEADLINE">DEADLINE:</SPAN> <2006-04-23 Sun> </a></H2>
which looks like
1 DONE eerste bandje volledig begrijpen <1 > DEADLINE: <2006-04-23 Sun>
notice the whitespace between 1 and >
>> When data can be retrieved back from an exported format, this would
>> be included /as/ /option/, as one will e.g. want to communicate to and
>> fro
>> with csv tables.
>I did not understand this one, sorry.
When a link like [[link][description]] is exported as such when
the link is in a table, there are two sides to this:
1. Looks ugly in csv
2. You would want to preserve the link (so not strip it of its
brackets) when having made changes to the table in some other
application, and then imported it again.
As these two sides are irreconcilable, I have opted to make only use
of internal radio links inside a table, which do not look ugly when exported.
One more point concerning link-export:
1. when exporting a link to a location in another file to html, this
will create a link in the html page which cannot retrieve its target
(which probably is due to html itself, but I do not know html that
well). Such links be better left out.
Thank you very much for your answers, and I will be happy to continue
contributing.
Regards,
Niels.
next prev parent reply other threads:[~2006-04-27 13:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 9:53 usage, ideas, suggestions, actually a braindumnp nielsgiesen
2006-04-27 10:30 ` Carsten Dominik
2006-04-27 13:02 ` nielsgiesen [this message]
2006-05-19 12:20 ` Carsten Dominik
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=20060427130238.92E602BDC@schimmel.ibbu.nl \
--to=nielsgiesen@ibbu.nl \
--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).