From: Michael Brand <michael.ch.brand@gmail.com>
To: "Tory S. Anderson" <torys.anderson@gmail.com>,
Uwe Brauer <oub@mat.ucm.es>,
emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: tables, comment in one line, export to html
Date: Wed, 27 Apr 2016 12:18:21 +0200 [thread overview]
Message-ID: <CALn3zojB4-Zgd+11zxtRZZN8MnrJrhqO+v=MejPmOh=M9oozbA@mail.gmail.com> (raw)
In-Reply-To: <87oa8vlb07.fsf@saiph.selenimh>
Hi Nicolas
I agree, together all the below makes sense. Some comments added.
Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> You are talking about section "3.5 The spreadsheet". I don't think this
> feature is directly related to spreadsheet capabilities.
>
> Actually, / in first column is described earlier in the manual, in "3.3
> Column groups". Besides, there is a similar feature described in "3.2
> Column width and alignment", about lines containing only alignment
> cookies:
>
> Lines which only contain these formatting cookies will be removed
> automatically when exporting the document.
<#> will have to be considered for removal of the line too.
> IMO, a better change would be to merge 3.2 and 3.3 as "Column
> operations" or some such, and add "<#>" as a way to ignore columns upon
> exporting. This way, everything related to columns is packed in the same
> subsection, and every column markup uses < or >. Moreover, there is no
> possible confusion with # markup from spreadsheet.
>
> WDYT?
> Another advantage about this is that there is no need for "/" in the
> first column, much like alignments cookies.
<#> will have to be fontified like <5> as org-formula (name and
description of the face are not precise) wich is the easiest part of
the change. Shouldn't < and > in a table be fontified too?
> It makes it simpler to ignore the first column.
Michael
next prev parent reply other threads:[~2016-04-27 10:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 11:08 tables, comment in one line, export to html Uwe Brauer
[not found] ` <6pkhucxunh.ln2@news.c0t0d0s0.de>
2016-04-19 13:40 ` Uwe Brauer
2016-04-19 13:42 ` Uwe Brauer
2016-04-26 16:25 ` Michael Brand
2016-04-26 16:49 ` Uwe Brauer
2016-04-26 16:55 ` Tory S. Anderson
2016-04-26 19:14 ` Nicolas Goaziou
2016-04-26 20:56 ` Michael Brand
2016-04-26 21:10 ` Nicolas Goaziou
2016-04-27 5:56 ` Michael Brand
2016-04-27 8:04 ` Nicolas Goaziou
2016-04-27 8:19 ` Nicolas Goaziou
2016-04-27 10:18 ` Michael Brand [this message]
2016-04-27 11:45 ` Nicolas Goaziou
[not found] <55d89bd56ed0429d8029b34af3a8f866@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-04-19 17:01 ` Eric S Fraga
[not found] ` <caa61e02395342579726b84d3cbca9e0@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-04-19 19:02 ` Eric S Fraga
2016-04-19 19:54 ` Uwe Brauer
[not found] ` <5fe8d3fe10224e88baac3f6665607e4d@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-04-20 7:38 ` Eric S Fraga
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='CALn3zojB4-Zgd+11zxtRZZN8MnrJrhqO+v=MejPmOh=M9oozbA@mail.gmail.com' \
--to=michael.ch.brand@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=oub@mat.ucm.es \
--cc=torys.anderson@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).