From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Oleh Krehel <ohwoeowho@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Is it possible to keep /all/ the heading properties in one place?
Date: Sun, 28 Feb 2016 09:59:00 +0100 [thread overview]
Message-ID: <87ziulb48b.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87h9gvrijp.fsf@gmail.com> (Oleh Krehel's message of "Fri, 26 Feb 2016 09:18:34 +0100")
Hello,
Oleh Krehel <ohwoeowho@gmail.com> writes:
> Already have been using it for years. I actually prefer outline.el to
> org-babel for most things now. But not for GTD - for that I need Org.
>
>> Alas, the Devil is in the detail:
>>
>> (example
>> ...
>> (properties ...))
>
> Not really. You see, the `beginning-of-defun' trick is: a defun is a
> thing that starts in the first column (that's why we escape all parens
> in the first column in Elisp). This trick has been working successfully
> for decades. It's both fast and simple.
It reminds me one mistake I made a couple years ago, when I changed
"key=value" to ":key value" in export attributes, for consistency with
Babel parameters.
When looking at
#+ATTR_LATEX: :key1 value1 :key2 value2
I thought it would be easy to parse it using `read', and get
a ready-to-use plist.
Unfortunately, users were required to tell the difference between
a symbol and a string (e.g., :key #value is invalid, so you need to
write :key "#value"), and to know the characters to quote in the strings
they would like to use.
Some users complained, and told me that "Org is not a programming
language". Fair enough. Org has, indeed, to strike a balance between
structure, required for efficiency and maintainability, and sloppiness,
needed when you want to quickly jot down notes in a document, or simply
let your ideas flow as you type, without hindrance.
In my experience, I think your suggestion would just repeat the very
same mistake. Yet, again, I may be wrong, so I guess you will have to
try and take the requirements for Org into consideration.
> Suggestion, and I've said it before, Org needs a standard simple inline
> kbd markup. Just like Markdown's <kbd></kbd> and Texinfo's @kbd{}.
> Since Org is tied into Emacs having an easy (and unambiguous) way to
> denote keyboard shortcuts would be very convenient.
This is export back-end specific. Org has no use for a "kbd" markup.
> Adding that would also progress the direction of having Org be the
> language for Emacs manuals. Right now, Org's own manual is in Texinfo,
> which is a shame since no one likes Texinfo and few people understand
> enough of it to get by.
Org can export to Texinfo. It can be helpful for those not understanding
well enough the latter.
> Do we have a way in Org to archive a heading form anywhere into a memoir
> format like this:
>
> * 2014
> ** 2014-01 January
> *** 2014-01-03 Thursday
> **** CANCELLED Foobar
> CLOSED: [2014-01-03 Fri 09:42] SCHEDULED: <2013-12-25 Wed>
> Added: [2013-08-08 Thu 17:38]
> **** DONE Baz
> CLOSED: [2014-01-03 Fri 17:12]
>
> Each heading is archived into level 4, on the day it was closed. I had
> it working a few years ago, relying on org-archive.el. But when I tried
> this week, it stopped working, so I had to rewrite it.
I suggest to start a bug report, if possible with an ECM demonstrating
the issue, in another thread.
> Thanks, I didn't know about it. It looks very similar to Racket's
> Scribble, and my own ElTeX.
Indeed, and they are all focused towards exporting. Export is but one
part of Org.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2016-02-28 8:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 10:59 Is it possible to keep /all/ the heading properties in one place? Oleh Krehel
2016-02-25 13:37 ` Nicolas Goaziou
2016-02-25 13:46 ` Oleh Krehel
2016-02-25 14:03 ` Nicolas Goaziou
2016-02-25 14:26 ` Oleh Krehel
2016-02-25 16:52 ` Nicolas Goaziou
2016-02-25 18:21 ` Eric S Fraga
2016-02-26 16:35 ` Rasmus
2016-02-28 9:35 ` Eric S Fraga
2016-02-28 11:32 ` Rasmus
2016-02-28 12:44 ` Eric S Fraga
2016-02-28 16:46 ` Rasmus
2016-02-28 17:05 ` Eric S Fraga
2016-02-25 19:17 ` Oleh Krehel
2016-02-25 20:16 ` Nicolas Goaziou
2016-02-26 8:18 ` Oleh Krehel
2016-02-28 8:59 ` Nicolas Goaziou [this message]
2016-02-28 12:17 ` Oleh Krehel
2016-02-28 16:34 ` Thomas S. Dye
2016-02-29 10:05 ` Nicolas Goaziou
2016-02-29 13:42 ` Thomas S. Dye
2016-02-29 15:00 ` Nicolas Goaziou
2016-02-29 13:53 ` Marcin Borkowski
2016-02-29 15:05 ` Nicolas Goaziou
2016-02-29 17:57 ` Revisiting moving manual to Org (was: Is it possible to keep /all/ the heading properties in one place?) Kyle Meyer
2016-02-29 17:17 ` Is it possible to keep /all/ the heading properties in one place? Achim Gratz
2016-02-29 18:01 ` Thomas S. Dye
2016-02-29 18:47 ` Nicolas Goaziou
2016-02-25 17:47 ` Michael Brand
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=87ziulb48b.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=ohwoeowho@gmail.com \
/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).