Nicolas Goaziou writes:
> Rasmus writes:
>
>> By this logic we'd have to add *every* "global" keyword, no? Does it make
>> sense?
>
> Every global (as in "ox.el") keyword should be documented there, indeed.
For now I have not moved the documentation as I'm not sure we know where
to put it yet.
Nicolas Goaziou writes:
> Rasmus writes:
>
>> By this logic we'd have to add *every* "global" keyword, no? Does it make
>> sense?
>
> Every global (as in "ox.el") keyword should be documented there, indeed.
OK.
Marc: you expressed a desire to fix some bugs. I don't know if you like
documenta
Rasmus writes:
> By this logic we'd have to add *every* "global" keyword, no? Does it make
> sense?
Every global (as in "ox.el") keyword should be documented there, indeed.
>>> At least SUBTITLE for ox-texinfo in not documented here.
>>
>> That's also a documentation bug. Note that it should p
Nicolas Goaziou writes:
>> I have now reviewed this section twice, and I have no clue what you want
>> me to change there. There's no :with-keywords or :with-description.
>
> I don't know either. I was sure that :keywords and :description were
> here, but, oddly, it isn't the case. That's a docum
Rasmus writes:
> I have now reviewed this section twice, and I have no clue what you want
> me to change there. There's no :with-keywords or :with-description.
I don't know either. I was sure that :keywords and :description were
here, but, oddly, it isn't the case. That's a documentation bug as
Hi,
Nicolas Goaziou writes:
>> First, as discussed a while back we want to move DESCRIPTION and KEYWORDS
>> out of ox.el as they are specific to certain backends. The first patch
>> does this.
>
> [...] You need to update (info "(org)Publishing options") accordingly,
> too.
I have now reviewed
Rasmus writes:
> Nicolas Goaziou writes:
>
>> Do you think that you /always/ want "pdfkeywords" to hold exactly the
>> same contents as what you could put in your document?
>
> You as in me: yes most certainly.
IIUC, it contradicts your initial post where you wanted, at some later
time, to add
Nicolas Goaziou writes:
> Do you think that you /always/ want "pdfkeywords" to hold exactly the
> same contents as what you could put in your document?
You as in me: yes most certainly.
> Do you think that a user who wants to fill pdfkeywords will always want
> to also add these contents in the
Rasmus writes:
> Keywords are akin to small headings to identify the contents of a
> document. I see no reason to restrict this to the reader of the
> electronic version of a document.
What are you talking about? I don't want to restrict anything: AFAIU,
the feature you propose already exists i
Nicolas Goaziou writes:
> Rasmus writes:
>
>> Nicolas Goaziou writes:
>>
>>> We don't need a convoluted markup for that, let's keep it simple.
>>
>> But then you'd have to repeat data. E.g.
>>
>> #+KEYWORDS: my keywords for meta-data that should also be printed.
>> my keywords for meta-data th
Rasmus writes:
> Nicolas Goaziou writes:
>
>> We don't need a convoluted markup for that, let's keep it simple.
>
> But then you'd have to repeat data. E.g.
>
> #+KEYWORDS: my keywords for meta-data that should also be printed.
> my keywords for meta-data that should also be printed.
>
> This s
Hello,
Rasmus writes:
> First, as discussed a while back we want to move DESCRIPTION and KEYWORDS
> out of ox.el as they are specific to certain backends. The first patch
> does this.
Thanks.
You can remove the keywords from "ox-org.el" and "ox-ascii.el", as they
do not use them. You need to
Nicolas Goaziou writes:
> We don't need a convoluted markup for that, let's keep it simple.
But then you'd have to repeat data. E.g.
#+KEYWORDS: my keywords for meta-data that should also be printed.
my keywords for meta-data that should also be printed.
This seems error prone and undesirable
Hi,
First, as discussed a while back we want to move DESCRIPTION and KEYWORDS
out of ox.el as they are specific to certain backends. The first patch
does this.
Second, I want to add support for printing keywords. This patch is still
rough (i.e. no need commenting), but before proceeding I want
14 matches
Mail list logo
