From: Matt Price <moptop99@gmail.com>
To: "Juan Manuel Macías" <maciaschain@posteo.net>,
"Org Mode" <emacs-orgmode@gnu.org>
Subject: Re: convert subtree or nested list to table
Date: Wed, 7 Jul 2021 17:16:43 -0400 [thread overview]
Message-ID: <CAN_Dec-dTtQxhummn6xWPxJg7Ha3HpLi73f7uWDEQ6doZ=k0+Q@mail.gmail.com> (raw)
In-Reply-To: <8735srsirf.fsf@posteo.net>
[-- Attachment #1: Type: text/plain, Size: 1499 bytes --]
thank you Juan Mnauel. I'm testing it out, but I do wonder if I would
really rather work with lists and some CSS!
On Tue, Jul 6, 2021 at 8:56 AM Juan Manuel Macías <maciaschain@posteo.net>
wrote:
> Hi Matt, sorry for the slow reply...
>
> Matt Price writes:
>
> > I'd love to try that, thanks. I think it would be really helpful.
> > Much appreciated!
>
> Some previous caveats:
>
> - *The code is very raw*. I wrote it almost as a "proof of concept" for
> my personal use, therefore it is quite improvable. In any case, it
> works (but i don't know if it will help you get what you want...).
>
> - The attached example is optimized to export to LaTeX. Use the tabularx
> environment, which is ideal for tables with a lot of textual content.
>
> - As for the code, there are two basic functions:
> `my-org/edit-table-cell' and
> `my-org/kill-edit-table-cell-buffer-and-save'. To edit an empty cell,
> you have to write something in that cell first.
>
> - The basic idea is that within each cell, the content is a single line
> (unfilled). In the edit buffer, the content is filled. There are two
> macros to indicate a line break and a paragraph end: {{{nl}}} and
> {{{par}}}. In the edit buffer you can put line breaks and white lines,
> but all of that is lost inside the cell once saved (all is a single
> line), so those macros are needed to indicate line or paragraph breaks
> (in LaTeX).
>
> Best regards,
>
> Juan Manuel
>
>
[-- Attachment #2: Type: text/html, Size: 1901 bytes --]
next prev parent reply other threads:[~2021-07-07 21:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 19:44 convert subtree or nested list to table Matt Price
2021-07-05 20:01 ` Juan Manuel Macías
[not found] ` <CAN_Dec8iqKS+3qvjkYvQxovegnEzqR_rra0Q-ZA9baPz1mXDAA@mail.gmail.com>
2021-07-06 12:56 ` Juan Manuel Macías
2021-07-07 6:18 ` Uwe Brauer
2021-07-07 18:27 ` Juan Manuel Macías
2021-07-07 18:44 ` Uwe Brauer
2021-07-07 21:16 ` Matt Price [this message]
2021-07-05 22:10 ` Tim Cross
2021-07-06 3:15 ` Matt Price
2021-07-06 5:10 ` Tim Cross
2021-07-06 11:00 ` Eric S Fraga
2021-07-06 11:49 ` Tim Cross
2021-07-06 11:50 ` Uwe Brauer
2021-07-07 21:17 ` Matt Price
2021-07-07 10:27 ` tbanelwebmin
2021-07-07 21:13 ` Matt Price
2021-07-08 9:27 ` tbanelwebmin
2021-07-08 12:22 ` Christian Moe
2021-07-20 15:11 ` Matt Price
2021-07-20 16:03 ` Nick Dokos
2021-07-20 17:03 ` Matt Price
2021-07-10 12:03 ` [a very different solution] (was: convert subtree or nested list to table) Uwe Brauer
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='CAN_Dec-dTtQxhummn6xWPxJg7Ha3HpLi73f7uWDEQ6doZ=k0+Q@mail.gmail.com' \
--to=moptop99@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=maciaschain@posteo.net \
/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).