From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [PATCH] Process hlines in imported tables
Date: Thu, 04 Apr 2013 23:01:17 +0200 [thread overview]
Message-ID: <866202ko2q.fsf@somewhere.org> (raw)
In-Reply-To: 87mwtepce2.fsf@gmail.com
Eric,
Eric Schulte wrote:
> I would agree that this (meaning raw implies scalar) should either occur
> for all languages or for none.
I think this is something interesting, but I wonder now if we wouldn't loose
more than we would win. I mean: how would one be able to output a real "raw"
result, then, that is one where pipes are not interpreted as table field
separator which have to be aligned in some specific way.
Do we need another argument for that?
I mean: at the end, raw should really be raw (no interpretation). If we want
some cycling for table alignment purpose (BTW, do you have lots of such code
blocks?), maybe it'd be better to introduce a `cycle' argument or so?
> If we do have such header argument implications, then we'd want to put them
> into the weakest portion of the default header argument hierarchy. Currently
> this hierarchy looks something like
>
> 1. default header arguments shipped with Org-mode
> 2. user-set default header arguments
> 3. default languages-specific header arguments shipped with Org-mode
> 4. user-set default language-specific header arguments
> 5. buffer or file level header arguments
> 6. subtree header arguments
> 7. code block header arguments
>
> I think this raw implies verbatim action should probably take place
> somewhere between 3 and 4, but there could be arguments for other
> positions. Also, without looking at the code, I'm not sure how
> difficult adding such implications would be.
Maybe I don't understand the problem correctly, but I'd think this "raw
implies verbatim" would have to take place after _each_ above step.
If between 3 and 4, then a raw specified on the block level (step 7) wouldn't
imply verbatim? Does that make sense?
I think every raw (be it default, language, buffer, subtree or block-local)
would have to imply the same reasoning.
> Are there other header argument implication rules which would make code
> blocks "do what I mean" more naturally in more situations?
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2013-04-04 21:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 1:46 [PATCH] Process hlines in imported tables Rick Frankel
2013-03-29 15:04 ` Eric Schulte
2013-03-29 21:42 ` Rick Frankel
2013-03-30 0:01 ` Eric Schulte
2013-03-30 23:41 ` Rick Frankel
2013-03-31 0:43 ` Eric Schulte
2013-03-31 12:29 ` Rick Frankel
2013-03-31 13:37 ` Eric Schulte
2013-04-01 16:22 ` babel results handling (was: Process hlines in imported tables) Rick Frankel
2013-04-03 14:18 ` babel results handling Eric Schulte
2013-04-03 18:02 ` Achim Gratz
2013-04-04 18:20 ` Rick Frankel
2013-04-03 18:21 ` [PATCH] Process hlines in imported tables Achim Gratz
2013-04-04 13:59 ` Sebastien Vauban
2013-04-04 15:02 ` Eric Schulte
2013-04-04 21:01 ` Sebastien Vauban [this message]
2013-04-06 16:30 ` Eric Schulte
2013-04-15 13:06 ` Sebastien Vauban
2013-04-15 15:25 ` Eric Schulte
2013-04-15 19:27 ` Sebastien Vauban
2013-04-04 18:35 ` Rick Frankel
2013-04-04 21:05 ` Sebastien Vauban
2013-04-04 19:29 ` Achim Gratz
2013-04-06 16:29 ` Eric Schulte
2013-04-06 17:07 ` Eric Schulte
2013-04-06 17:24 ` Bastien
2013-04-06 17:39 ` Eric Schulte
2013-04-04 18:30 ` Rick Frankel
2013-04-04 20:27 ` Sebastien Vauban
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=866202ko2q.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).