moment.
We should strive to provide a broad enough out-of-the-box experience
first.
> The function that handles the export doesn't look to complicated after
> all.
Indeed! It's a wonder no one implemented it earlier. ;)
Regards,
--
Nicolas Goaziou
Hello,
"Bruce D'Arcus" writes:
> On Tue, May 18, 2021 at 11:45 AM Nicolas Goaziou
> wrote:
>
>> I didn't test it much so it probably contains silly bugs. Sorry about
>> that.
>
> OK, a simple bug report.
>
> cite/bare -> \cite (currently is
URL is
not good idea. Yet, some users may want to use Unicode symbols in
a target.
Regards,
--
Nicolas Goaziou
Axel Kielhorn writes:
>> Am 20.05.2021 um 19:58 schrieb Nicolas Goaziou :
>>
>> Org Duration is strict about what it is fed with (which is good). Effort
>> property expects a duration as value. But "3-8" is not a valid duration.
>> However, &qu
<> really remains
> "target" as in id="target" instead of a random ID?
See `org-html-prefer-user-labels'.
Regards.
--
Nicolas Goaziou
/test-org-list.el#L1207
I probably missed that re-definition. Feel free to disregard my comment.
Regards,
--
Nicolas Goaziou
58e5 Marco Wahl
> 12.02.2017, 09:19
>
> In
>
> Use Org duration library 7e8cf5f4c Nicolas Goaziou
> 13.02.2017, 14:41
>
> neither column view nor dynamic block is working.
>
>
>
> For the column view this was fixed in:
>
> Merge
ain | | cite |
> |---+---+--|
> | (default) | caps | Autocite |
> | (default) | | autocite |
>
> Well, see the revised table above. WDYT?
I'm fine with it. But I see a long discussion ensued. So, is it too
early to settle on this one, or shall I implement it?
Regards,
--
Nicolas Goaziou
urrently (but it seems necessary in general)
There is `org-cite-biblatex-options' defcustom. Currently, it defaults
to nil, but you can set it to, e.g., "key=value,key2=value" if needed.
We can also change the default.
Regards,
--
Nicolas Goaziou
Fixed. Thank you.
> but which places are *forbidden* the doc string does not say much.
`org-footnote--allow-reference-p' is very permissive. Footnote are
allowed anywhere it makes sense, I think. The function is also well
documented, you may want to look at the source if you have doubts.
Regards,
--
Nicolas Goaziou
Denis Maier writes:
> In that case, I'd think that note/bare => footcitecite isn't
> a particular good fit. Footcitetext puts the citation in a footnote,
> just that it doesn't print a footnote mark in a running text.
> (This is useful in cases where the regular footnote mechanism in LaTeX
>
uot; variant means "without parenthesis", I think.
One problem is there is no "\cite", or "\parencite". I though they would
make a good fit for the default style, "\cite" being the "bare" variant
of "\parencite", and "\autocite" could be moved to a "auto" style. I'm
not sure where to put \cite, then.
Suggestions to change the table above are welcome.
Regards,
--
Nicolas Goaziou
dictable? Also, adding
#+cite_export biblatex ... auto
to trigger autocite by default seems easy enough. In any case, feel free
to suggest more styles/types to the list.
Is there any crucial feature missing?
I didn't test it much so it probably contains silly bugs. Sorry about
that.
Feedback is highly appreciated.
Regards,
--
Nicolas Goaziou
is updated every Monday, you need to update it again
(later?) today to get the fix.
Regards,
--
Nicolas Goaziou
Hello,
Joost Kremers writes:
> On Sun, May 16 2021, Nicolas Goaziou wrote:
>
>> So... let's get liberal and say a key must match:
>>
>> (rx "@" (one-or-more (any word "-.:?!`'/*@+|()<>&_^$#%&~")))
>>
>> Nothing bad co
info)
tree))
--8<---cut here---end--->8---
Also, when "org-cite-wip" is merged, you will be able to replace, e.g.,
(funcall create-export-snippet "%fontfeature start\n")
with
(org-export-raw-string "%fontfeature start\n")
Regards,
--
Nicolas Goaziou
;>&_^$#%&~")))
Nothing bad could happen, right?
[¹] https://lists.gnu.org/archive/html/emacs-orgmode/2015-03/msg00131.html
--
Nicolas Goaziou
"Bruce D'Arcus" writes:
> I was just interacting with one of the org-roam-bibtex developers about
> org-cite.
>
> He noted that citekeys can only start with an underscore or alpha character.
>
> Is that a necessary restriction?
>
> He, it turns out, mostly has keys of the form '2020-DOE-ABC".
Hello,
"Bruce D'Arcus" writes:
> On Sat, May 15, 2021 at 5:29 PM Nicolas Goaziou
> wrote:
>> I pushed in "wip-cite-new" an attempt to parse styles as a pair (name .
>> variant). I also updated oc-natbib.el and oc-basic.el accordingly.
>
> Looks g
Ihor Radchenko writes:
> Nicolas Goaziou writes:
>> It should be a paragraph. I'll fix it soon.
>>
>> Note the problem can be reproduced with only
>>
>> * test
>> :end:
>
> Thanks!
Fixed. Thank you.
> Also, I have few more questions (or
ement-at-point at the beginning of ":end:" line
> yields (drawer ...).
It should be a paragraph. I'll fix it soon.
Note the problem can be reproduced with only
* test
:end:
Regards,
--
Nicolas Goaziou
Hello,
Bastien writes:
> Hi Nicolas,
>
> Nicolas Goaziou writes:
>
>> Ah! I forgot the link part! Hopefully done here.
>>
>> (defun org-sort-remove-invisible (s)
>> "Remove emphasis markers and any invisible property from string S.
>> Assume S
;b")) "\\citeyear")
(`(,(or "year" "y") . ,_) "\\citeyearpar")
;; Default ("nil") style.
(`(,_ . ,(or "bare" "b")) "\\citealp")
(`(,_ . ,(or "caps" "c")) "\\Citep")
(`(,_ . ,(or "full" "f")) "\\citep*")
(`(,_ . ,(or "bare-caps" "bc")) "\\Citealp")
(`(,_ . ,(or "bare-full" "bf")) "\\citealp*")
(`(,_ . ,(or "caps-full" "cf")) "\\Citep*")
(`(,_ . ,(or "bare-caps-full" "bcf")) "\\Citealp*")
(`(,_ . ,_) "\\citep")
;; This should not happen.
(_ (error "Invalid style: %S" style)))
--8<---cut here---end--->8---
So now, you can write a cryptic [cite/t/bcf:@key] and get
\Citealt*{key}.
Feedback welcome, as always.
Regards,
--
Nicolas Goaziou
with Org
> inserting text in the temporary buffer.
Could you show the backtrace? I fail to see when prog-mode-hook is
called.
Regards,
--
Nicolas Goaziou
point (correctly) returns (table-row (...)).
I'm not sure to understand your report, but `org-element-at-point'
should return a `table' element at the very beginning of a table (here
at the beginning of the first row), not a `table-row'.
Regards,
--
Nicolas Goaziou
Hello,
Denis Maier writes:
> Am 13.05.2021 um 23:33 schrieb Nicolas Goaziou:
>> Hello,
>> [...]
>>RULE is a triplet of symbols (PUNCT POSITION RELATIVE):
>> PUNCT is the desired location of the punctuation with regards
>> to the
>> quotation
-register-processor 'test
:export-citation #'org-test-export-citation)
--8<---cut here---end--->8---
I'll comment further in another message.
Regards,
--
Nicolas Goaziou
branch
> 2. ran make
You probably need to reload Org (M-x org-reload) at this point.
> 3. evaled your "test" code
> 4. ran the export
Regards,
--
Nicolas Goaziou
ete sentence." [cite:@key]
"This is an incomplete sentence" [cite:@key].
This is a complete sentence. [cite:@key]
This is an incomplete sentence [cite:@key].
--8<---cut here---end--->8---
and changing language value.
WDYT?
Regards,
--
Nicolas Goaziou
Nicolas Goaziou writes:
> Stephen Eglen writes:
>
>>> I solved this part on maint branch.
>>
>> Thank you!
>
> And I reverted it because the "fix" introduced other issues!
I pushed another fix. *crossing fingers*
Regards,
s an error
>
> org-duration-to-minutes: Invalid duration format: #("10:35-11:50" 0 11
> (fontified nil line-prefix #(" " 0 2 (face org-indent)) wrap-prefix
> #(" " 0 2 (face org-indent)) org-category "cal-gmail"))
> SPC ESC is undefined
This was fixed earlier today. You may want to update Org.
Regards,
--
Nicolas Goaziou
Hello,
Timothy writes:
> Going off this, I've taken this as assent and just pushed my patch in
> its current form as 981f25031.
Thank you.
Regards,
--
Nicolas Goaziou
Do you still find concatenation prefix-only concatenation more
appropriate? Also, what would happen with multiple keys?
Regards,
--
Nicolas Goaziou
Hello,
Stephen Eglen writes:
>> I solved this part on maint branch.
>
> Thank you!
And I reverted it because the "fix" introduced other issues!
To be continued…
Regards,
--
Nicolas Goaziou
questions other #orgmode?
I don't know, but this mailing list is a fine place to ask questions.
Regards,
--
Nicolas Goaziou
ul to insert a blank line within a list item.
OTOH, on the third newline, you are really out of the list.
Regards,
--
Nicolas Goaziou
already exist. Sub-styles requires more work. Does the
benefit outweigh it? If so, what do you suggest for the inheritance
problem?
Regards,
--
Nicolas Goaziou
fault
> duration by setting org-agenda-default-appointment-duration."
Sure. Patch welcome.
Regards,
--
Nicolas Goaziou
I can't figure this bit out though.
>
> '[cite:/Text@doe]' is obvious and elegant enough, but how do you do
> the same thing for default?
This is no longer the default style, but a "caps" style, so it would be
[cite/caps:...]
>
> But with some kind of sub-style, you can do:
>
> [cite//c:@doe]
>
> Bruce
>
Regards,
--
Nicolas Goaziou
When I try to use a custom drawer and export to HTML the contents of the
> drawer is
> output to the resulting HTML. But not the drawer name and end tags.
See `org-export-with-drawers'.
Regards,
--
Nicolas Goaziou
Hello,
Timothy writes:
> I just thought there may be people who like me are interested in
> s for LaTeX in HTML, but not in Markdown.
Fair enough. Let's push your last patch, then.
Thank you.
Regards,
--
Nicolas Goaziou
"Bruce D'Arcus" writes:
> On Thu, May 6, 2021 at 10:12 AM Nicolas Goaziou
> wrote:
>
>> You're missing the colon at the end of the keyword. Note that `org-lint'
>> warns you about it.
>
> Ugh; sorry about that.
>
> I'm getting out of my depth, as I
"Bruce D'Arcus" writes:
> On Thu, May 6, 2021 at 8:05 AM Nicolas Goaziou wrote:
>
>> Your document doesn't contain a "#+print_bibliography" keyword. It is
>> responsible for adding the "\\bibliography{...}" macro. I don't think it
>> is poss
y for the
> benefits.
I'm still not convinced by the benefits. Could you describe a situation
where sub-styles would be really beneficial?
Regards,
--
Nicolas Goaziou
Hello,
"Bruce D'Arcus" writes:
> To come back to this
>
> On Wed, May 5, 2021, 10:53 AM Nicolas Goaziou
> wrote:
>
> Also it introduces ambiguities in style inheritance.
>> For example, if I add
>>
>> #+cite_export: natbib pla
rd. It is
responsible for adding the "\\bibliography{...}" macro. I don't think it
is possible to produce a PDF without it.
Regards,
--
Nicolas Goaziou
ove.
Also, completion front-ends can alleviate the burden of memorizing all
those styles.
Anyway, for now it's sub-styles. Please let me know what you think about
them, and about the processor, in general. I couldn't test it much
because the test bibliography I have is apparently "not compatible with
author-year citations".
As a reminder, to test it, you (require 'oc-natbib) to register the
processor, and add "#+cite_export: natbib" in your document (or set
`org-cite-export-processor' to (natbib)).
Regards,
--
Nicolas Goaziou
bout is
really the bibliography style.
Does that make sense?
Regards,
--
Nicolas Goaziou
Hello,
"Bruce D'Arcus" writes:
> On Tue, May 4, 2021 at 12:59 PM Nicolas Goaziou
> wrote:
>
>> AFAIU, the idea is to use styles from you wiki. However, sub-styles are
>> not mentioned. They could be "full" for the starred variants, "caps&quo
on contains the global prefix and suffix, each
reference contains the local prefix and suffix, and the citation key.
You can then use functions like `org-cite-get-references' and
`org-cite-key-boundaries' on them, in addition to usual
`org-element-property'.
Regards,
--
Nicolas Goaziou
"Bruce D'Arcus" writes:
> On Tue, May 4, 2021 at 12:59 PM Nicolas Goaziou
> wrote:
>> Is the default \cite{key} command (without any other package) used? I'm
>> not sure we should provide it since we are working towards more complete
>> solutions.
>
> N
are in common use, processors might as well declare them in
`org-cite-register-processor' as a help for, e.g., functions inserting
citations. Hmm.
WDYT?
Regards,
--
Nicolas Goaziou
quot;oc.el" provides a number of hopefully useful tools. Among them,
`org-cite-list-bibliography-files' function returns what you're asking
for. Global variable and keywords are cumulative.
HTH!
Regards,
--
Nicolas Goaziou
Eric S Fraga writes:
> On Tuesday, 4 May 2021 at 07:58, Bruce D'Arcus wrote:
>> Perhaps the bibtex/biblatex folks can help with those details?
>
> For natbib, there is a good summary at
>
> http://merkel.texture.rocks/Latex/natbib.php
Thanks.
Naive question: it doesn't say how to print the
for such objects, because
we're outside the specification anyway. I'd rather not overdo it.
WDYT?
Regards,
--
Nicolas Goaziou
different cases:
[cite:@key] => ???
[cite:prefix @key suffix] => ???
[cite:global; prefix @key1; @key2; suffix] => ???
Ditto for "print_bibliography" keywords. I think you get the idea.
Regards,
--
Nicolas Goaziou
Nicolas Goaziou writes:
> Oops. I'll fix it in a few hours. I need to treat LaTeX-derived
> back-ends specially in the context of BibTeX files.
>
> I'll let you know when it's done.
Done.
Hello,
"Bruce D'Arcus" writes:
> On Mon, May 3, 2021 at 12:42 PM Nicolas Goaziou
> wrote:
>
>> Anyway, I suggest to let it nil, and select it at the document level
>> instead, with
>>
>> #+cite_export: basic bibstyle citestyle
>
&g
Timothy writes:
> Actually, since writing this patch I'm not sure that $$-surrounding
> \begin{}...\end{} environments is also a good idea. I'm inclined to
> leave this out of the patch.
Sounds good.
> I do rather like the `rx' macro, however I'm not sure that
> (rx bol "\\(") is really an
"Steven Bagley" writes:
> I am aware of the meaning of "::". Is this a design decision or an
> implementation constraint? My intuition, obviously wrong here, is that
> link, being a special kind of object, should have priority over what
> amounts to a formatting command.
- ... :: is also a
all of them in the bibliography).
I don't know how to do that cleanly. However, I think this is already
too smart a feature for "basic" back-end. So, I'd like to punt on this
one.
Regards,
--
Nicolas Goaziou
taining entries of different types.
Regards,
--
Nicolas Goaziou
.
You are missing some cases. The fragment could be $...$ or $$...$$
already, so you can return it as-is without sending the message.
Otherwise, it is a macro. We can assume it lives outside math mode. So
maybe the "Unrecognized fragment: %S" is in order in that situation. We
could also let HTML export back-end deal with it. I don't know what is
better.
WDYT?
Regards,
--
Nicolas Goaziou
k found".
>
> Confirmed, thanks for the reproducible recipe.
An item bullet followed by two colons is a special syntax in Org. It has
precedence over the link.
Besides saying "don't do that", the usual trick is to insert a zero
width space between the two colons.
Regards,
--
Nicolas Goaziou
-path (expand-file-name dir org-root)
--8<---cut here---end--->8---
> I guess this is a broader question: how do org developers test their
> branches?
Since I use development Org, I simply checkout the branch, run "make &&
org-reload", and test it.
Regards,
--
Nicolas Goaziou
Tom Gillespie writes:
> Yes. My question is about how to deal with cases like
>
> --8<---cut here---start->8---
> 1. foo
>
> #+begin_src emacs-lisp
> (+ 1 1)
> #+end_src
>
> 2. bar
> --8<---cut here---end--->8---
>
espace is required, user beware. A final
> aside: maybe plain lists could have the #+begin_ and #+end_
> lines indented to the level of the plain list but maybe not the body?
What makes you think this is not the case?
Regards,
--
Nicolas Goaziou
quot;maint" branch,
however. Also, a proper commit message would be nice. Could you send an
updated patch?
Moreover, have you signed FSF papers already? This is above limit for
tiny changes.
Regards,
--
Nicolas Goaziou
Eli Zaretskii writes:
>> From: Nicolas Goaziou
>> Cc: shingo@gmail.com, 48...@debbugs.gnu.org
>> Date: Sun, 02 May 2021 14:18:24 +0200
>>
>> My problem is that I have some string, _which is not displayed anywhere_
>> yet. I need to obtain its real wi
Hello,
"Bruce D'Arcus" writes:
> Nicolas - just a little question on one detail:
>
> On Thu, Apr 29, 2021 at 10:06 AM Nicolas Goaziou
> wrote:
>
>> On a citation key, "follow" capability moves point to the
>> corresponding entry in the curr
Eli Zaretskii writes:
> I'm not sure what kind of example is necessary. How about if you ask
> specific questions about the arguments of that function which you
> don't understand clearly how to use?
Fair enough. However, i don't think my misunderstanding is related to
arguments of that
Hello,
Timothy writes:
> Nicolas Goaziou writes:
>
>> I pointed out some concerns I have about the robustness of this system
>> already. I don't think you answered to any of them. I fear we may be
>> communicating past each other in this thread.
>
> Sorry a
you mind giving an example about `window-text-pixel-size' usage in
this situation?
AFAIU, `window-text-pixel-size' returns the size of the window, but
I fail to see how it is relevant here. Note that `text-width' in the
code above is not related to the width of the window, but is a maximum
number of allowed characters on a line.
Thank you!
Regards,
--
Nicolas Goaziou
Timothy writes:
> Nicolas Goaziou writes:
>
>> I don't think such a system would preserve properties offered by
>> `org-export-get-reference', for example in non-latin languages. Also,
>> header content is not stable enough: when you're linking to the custom
>>
not enabled.
>
> I am investigating now but I thought I would post this as a bug
> regardless. The trace below is for the release of org-mode with
> 28.0.50, but I can confirm that it is the same on the current master.
FWIW, I confirm this, too. This has bugged me for a long time now!
Regards,
--
Nicolas Goaziou
Hello,
Timothy writes:
> Nicolas Goaziou writes:
>
>> With the above in mind, I think there are two ways to "improve TOC links
>> stability":
>>
>> 1. Improve the system behind `org-export-get-reference', e.g., so it
>>behaves bette
ybrid system in HTML exporter, much like Texinfo's.
Those two ways are orthogonal; both may solve the current issue
independently on the other. My gut feeling is the second way is easier
to achieve, at least on the short term.
Regards,
--
Nicolas Goaziou
ers
to consider moving around, with rules explaining if they should be
included in a preceding quote.
Since this would be backward compatible, we don't need to implement it
for now if the use-case is, at this point, purely hypothetical.
Thank you for the feedback!
Regards,
--
Nicolas Goaziou
ut it.
WDYT?
Regards,
--
Nicolas Goaziou
Hello,
Ramesh Nedunchezian writes:
> Bug: Texinfo export: Inline images are NOT rendered in INFO viewer
Fixed. Thank you.
Regards,
--
Nicolas Goaziou
s a test.[9]
[10].
This is a « test »[11]
--8<---cut here---end--->8---
Is it what you had in mind?
Also, I have questions about punctuation.
Currently, these changes only apply to terminal punctuation I could
think of: . ! ? ... …
Should the above apply to any punctuation, i.e., [:punct:]? Should it be
limited to a different set of elements instead? If so which one? Should
it be configurable?
Regards,
--
Nicolas Goaziou
creating internal references, which relies on randomness + cache. But it
explicitly removes internal references not actually used from there (see
`org-publish--store-crossrefs'). Keeping those references instead would
make all links stable, of course.
Regards,
--
Nicolas Goaziou
use `info'
>function directly.
You can add, e.g,
("info" . (lambda (file _) (info file)))
to `org-file-apps'.
Regards,
--
Nicolas Goaziou
cut here---end--->8---
As pointed out above, don't expect too much from it. Nevertheless,
feedback is welcome. Improvements are welcome too, but at this point,
I would suggest to spend energy porting "citeproc-org" or "org-ref" to
this API instead.
Regards,
--
Nicolas Goaziou
).
Indeed. I couldn't spot this.
I applied your patch.
Thank you!
Regards,
--
Nicolas Goaziou
this is not a proper fix for the problem, as discussed in
the thread.
Regards,
--
Nicolas Goaziou
Hello,
Alex writes:
> In the definition of |org-info-store-link|, when calling
> |org-link-store-props|, the |:desc| key is given whereas I think
> |:description| was intended.
You're right. This should now be fixed. Thank you.
Regards,
--
Nicolas Goaziou
`org-slimhtml-publish-to-html'.
> There is something i don't understand in the processing of "translate-alist",
> so perhaps if the derived backend doesn't
> implement a footnote-reference function, i cannot extend it ?
You should be able to extend it.
Regards,
--
Nicolas Goaziou
er, not an existing one. But hey, it worked!
Do you know what could cause this?
Regards,
--
Nicolas Goaziou
Hello,
"Cheong Yiu Fung" writes:
> Subject: [PATCH] org-manual.org: add hints for visible-only export
I tweaked your commit messages and applied your patches.
Thank you.
Regards,
--
Nicolas Goaziou
l regexp) end t)
You can drop the `eval'.
>(when (and (called-interactively-p 'any)
> - (not (string-match-p (rx "." (or "txt" "tsv" "csv") eos) file)))
> + (not (string-match-p (rx "." (or "txt" "tsv" "csv") eos) file))
> + (not (yes-or-no-p "File does not havs .txt .txt .csv as
> extension. Do you still want to continue? ")))
"does not have" and ".txt" -> ".tsv" I guess.
Also please provide a patch with a commit message, possibly using `git
format-patch'.
Thanks!
Regards,
--
Nicolas Goaziou
Maxim Nikulin writes:
> On 27/04/2021 22:52, Nicolas Goaziou wrote:
>> Maxim Nikulin writes:
>>> My expectation is to get
>>> link to org-beginning-of-line if help is invoked from an org buffer
>>> and link to beginning-of-line if I came to the help pag
know whether associated function may be obtained
> for a help buffer opened for keystroke.
I did this on master. I only tested it lightly.
Regards,
--
Nicolas Goaziou
nds like ox-gfm.
That is the idea. "ox-md" is here to do the boring tasks, while being as
neutral as possible. There no need to handle specific syntax since you
can easily create a derived back-end.
> Basically: markdown is a mess and I'm not sure what would be a good
> course of action.
Regards,
--
Nicolas Goaziou
he processor, as a sixth (!)
argument, and let it deal with it.
--
Nicolas Goaziou
Denis Maier writes:
> Oh, and what do you think regarding the multiple bibliographies
> question?
As far as Org is concerned, you can have multiple "bibliography"
keywords, e.g.,
#+bibliography: file1.bib
#+bibliography: file2.bib
Internally, the bibliography is stored as a list of
(format "(%s%s, %s%s)"
(org-export-data prefix info)
(org-export-data author info)
year;I assume year cannot contain problematic characters
(org-export-data suffix info))
So, nothing impossible, but still slightly inconvenient.
Regards,
--
Nicolas Goaziou
rate check would be:
(and (< (point) (org-element-property :post-affiliated context))
(org-match-line (rx (zero-or-more (any " " "\t")) "#+plot:")))
Regards,
--
Nicolas Goaziou
.
So that would be an argument for keeping suppress-author.
Regards,
--
Nicolas Goaziou
or not, perhaps
according to language.
Regards,
--
Nicolas Goaziou
301 - 400 of 9712 matches
Mail list logo
