From: "Rolf Sander (MPI)" <rolf.sander@mpic.de>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Fwd: comment lines inside org tables
Date: Wed, 5 Oct 2016 14:30:55 +0200 [thread overview]
Message-ID: <02ef963d-cb72-4e3c-75a4-c4759e02b07a@mpic.de> (raw)
In-Reply-To: <87wphpimua.fsf@ucl.ac.uk>
Hello Eric,
> could you not simply use the / label and then have a comment in one of
> the existing columns, a column that is width restricted so that a
> large amount of text doesn't affect alignent? You can then use the
> special edit mode (C-c `) for long entries to see the full comment.
Thanks for the suggestion. Yes, I could do this and see something like
this in emacs:
|---+--------------+-------+--------|
| | <12> | | |
| | animal | size | number |
|---+--------------+-------+--------|
| | gnus | big | 3 |
| / | don't forg=> | | |
| | gnats | small | 1000 |
|---+--------------+-------+--------|
The real contents of the file, however, would look very different:
|---+--------------+-------+--------|
| | <12> | | |
| | animal | size | number |
|---+--------------+-------+--------|
| | gnus | big | 3 |
| / | don't forget to add elephants here: | | |
| | gnats | small | 1000 |
|---+--------------+-------+--------|
Since I am sharing my table with several colleagues at work, it is
important that the columns are really aligned in the file (not only when
viewing the file in org-mode). Unfortunately, not all of my colleagues
are using emacs...
I am still waiting for an answer to my question if the solution with
"|-/" comments that I have proposed has any negative side effects...
Best regards
Rolf
--
-----------------------------------------------------------------------
Rolf Sander phone: [+49] 6131/305-4610
Max-Planck Institute of Chemistry email: rolf.sander@mpic.de
PO Box 3060, 55020 Mainz, Germany homepage: www.rolf-sander.net
-----------------------------------------------------------------------
www.atmospheric-chemistry-and-physics.net
www.geoscientific-model-development.net
-----------------------------------------------------------------------
next prev parent reply other threads:[~2016-10-05 12:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 8:05 comment lines inside org tables Rolf Sander (MPI)
2016-09-27 10:56 ` Fwd: " Rolf Sander (MPI)
2016-09-27 11:31 ` Nicolas Goaziou
2016-09-27 12:06 ` Rolf Sander (MPI)
2016-09-27 21:36 ` Nicolas Goaziou
2016-09-30 14:52 ` Rolf Sander
2016-09-30 15:36 ` Nicolas Goaziou
2016-10-02 19:23 ` Rolf Sander
2016-10-03 13:16 ` Rolf Sander (MPI)
[not found] ` <6cd445a96b6d4cd88b912298ee4f4df1@DB5PR01MB1895.eurprd01.prod.exchangelabs.com>
2016-10-03 13:27 ` Eric S Fraga
2016-10-05 12:30 ` Rolf Sander (MPI) [this message]
2016-10-05 14:58 ` Nicolas Goaziou
2016-10-05 15:32 ` Rolf Sander (MPI)
2016-10-05 16:10 ` Thomas S. Dye
2016-10-05 16:29 ` Nicolas Goaziou
-- strict thread matches above, loose matches on Subject: below --
2016-09-27 11:18 John Kitchin
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=02ef963d-cb72-4e3c-75a4-c4759e02b07a@mpic.de \
--to=rolf.sander@mpic.de \
--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).