David Masterson writes:
> My use-case is this:
>
> I'd like to use Org to write up *all* the information about my family
> life (so to speak) including medical histories of my family, issues with
> the house, bank accounts, financial information, etc., so that my family
> has all the
I'll try to explain my view of tags. Let's see if it makes sense. :)
Conceptually, properties are like a generic key-value store for
headings, and tags are like a certain property. Imagine if, instead of
tags being placed in headings, like this:
* Blueberries :food:fruit:
...tags were
On Friday, 20 Dec 2019 at 17:28, Stefan Nobis wrote:
> Hmmm... but it should be solvable. Maybe something along the lines of
> this (rough sketch, I have next to no experience with the org code
> base):
It should be solvable and something like what you have written looks
promising. But it's
I might add that a properties/drawer is a sort of "official heading
metadata repo," while tags not so much. It would be nice to see (lots of)
examples.
On Fri, Dec 20, 2019 at 9:18 AM Ken Mankoff wrote:
>
> On 2019-12-19 at 22:24 -08, Lawrence Bottorff
> wrote...
> > Very simple, largely
"Fraga, Eric" writes:
> However, it seems that simply adding \relax does not work if there
> is an \hline immediately following so the solution is not that
> straightforward.
Hmmm... but it should be solvable. Maybe something along the lines of
this (rough sketch, I have next to no experience
On Friday, 20 Dec 2019 at 15:29, Stefan Nobis wrote:
> As the org-table does not support all the fancy features of LaTeX
> tables and the LaTeX row/line break is generated implicitly, I would
> say the LaTeX export should always emit the additional \relax.
I agree. I shouldn't have to be this
On 2019-12-19 at 22:24 -08, Lawrence Bottorff
wrote...
> Very simple, largely philosophical question: When/why use a properties
> drawer below a heading versus just using tags on the heading? What are
> the advantages, disadvantages of both?
Tags are binary. They are there or not.
Property
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
On Friday, 20 Dec 2019 at 13:33, Joost Kremers wrote:
> Few people seem to realise that the double backslash `\\` in LaTeX is
> a macro that can actually take an optional argument, a measure
> specifying the height of the newline.
Ah ha! That makes perfect sense. Thank you.
--
Eric S Fraga
"Joost Kremers" writes:
> The solution I usually opt for is to enclose the brackets in an
> additional set of braces: `{[...]}`. Whether Org export can and
> should automate that, I can't say.
In the generated LaTeX adding a '\relax' (so each line ends with
'\\\relax') would be a another
On Fri, Dec 20, 2019, at 12:56 PM, Fraga, Eric wrote:
> #+begin_src latex
> \documentclass{scrartcl}
> \begin{document}
> % packages deleted, none of which is used anyway in the following
> \tableofcontents
>
> \section{some results}
> \label{sec:org4f5891c}
> \begin{table}[hbtp]
>
Hello all,
this may not belong in this mailing list as it's arguably a LaTeX issue
but I'm having a problem exporting a table to PDF via LaTeX. I hope
somebody can help me out.
I've reduced my problem file to a small (hopefully minimal) example and
verified this with emacs -Q, using emacs 27.x
On Fri, Dec 20, 2019 at 3:25 PM Lawrence Bottorff wrote:
>
> Very simple, largely philosophical question: When/why use a properties drawer
> below a heading versus just using tags on the heading? What are the
> advantages, disadvantages of both?
I believe tag filtering has better performance
Hello Org!
I attached a patch that is required to get ox-odt to work on
guix/nix/other distributions where package files are placed in a
read-only directory. After the file styles.xml is copied to /tmp, now
we set read-write permissions to it before trying to write it. Before
this patch, we got
[Forwarding this to emacs-devel]
The naming convention for mode-specific bug reporting seems to be
confusing. The bug reporting functions are often not easy to discover
without knowing the explicit command name (especially with emacs default
completion interface). For example see recent message
16 matches
Mail list logo
