emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Michael Brand <michael.ch.brand@gmail.com>
Cc: Uwe Brauer <oub@mat.ucm.es>,
	emacs-orgmode <emacs-orgmode@gnu.org>,
	"Tory S. Anderson" <torys.anderson@gmail.com>
Subject: Re: tables, comment in one line, export to html
Date: Tue, 26 Apr 2016 23:10:30 +0200	[thread overview]
Message-ID: <87wpnkkreh.fsf@saiph.selenimh> (raw)
In-Reply-To: <CALn3zoj6XQ5Tz4ffA2on2Kto2A6GuDY0aqfgUxQb+BiObLjNNA@mail.gmail.com> (Michael Brand's message of "Tue, 26 Apr 2016 22:56:54 +0200")

Hello,

Michael Brand <michael.ch.brand@gmail.com> writes:

> # in non-first columns to mean noexport of the column has the
> disadvantage of possible confusion with # in the first column where it
> means special effect for recalculation when using the spreadsheet. As
> I understand your first paragraph you want to avoid such confusion.

I don't think there is a possible confusion if the manual makes it
clear.

> <#> I find a bit too near to <5>, <, > or <>.

That was exactly the point, since those all apply to columns, unlike to
rows special markers. IOW, so far, columns syntax systematically uses <
or > (or both).

> % or ; used for comments in LaTeX or Emacs Lisp I would find a good
> space saving single character alternative. Why not % as this would not
> be the first time that Org borrowed some syntax elements from LaTeX?

Org comment syntax is related to #, not % or ;. I'd rather have similar
things look similar.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2016-04-26 21:10 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 [this message]
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
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=87wpnkkreh.fsf@saiph.selenimh \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=michael.ch.brand@gmail.com \
    --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).