(org-element-context) instead of direct call to citation
> parser.
This is morally equivalent to use the parser for fontification, which is
the long-term solution exposed before.
Regards,
--
Nicolas Goaziou
' or `org-cite-activate'.
A long-term solution would be to apply fontification on top of parsed
data exclusively. IIRC, I think Ihor started to work on something like
this, but I don't know about the current state of that project.
Regards,
--
Nicolas Goaziou
Ihor Radchenko writes:
>> I think the zero-width space can be inserted on the other side.
>
> Could you elaborate? In the following example, inserting zero-width
> space at *bold will break the intended bold emphasis *bold ... here*.
>
> Some *bold emphasis with reference [cite/citet*:@key] will
Ihor Radchenko writes:
> Nicolas Goaziou writes:
>
>>> Rudolf Adamkovič writes:
>>>
>>> The idea sounds good and having tests is very good. Though I am not
>>> expert in texinfo. CC-ing Nicolas. He is the maintainer.
>>
>> My Texinfo 6.
rting zero-width space will not only be awkward here, but
> also breaks parser: e.g. [cite/citet:@key] is not currently
> recognised as a citation.
I think the zero-width space can be inserted on the other side.
If there's no objection, I'll add asterisk character to the list of
allowed characters in citation style.
More generally, what other characters should be allowed ?
Regards,
--
Nicolas Goaziou
relatively long
>> experience with org->latex.
>
> Sorry for the late answer and thanks for proposing this.
>
> I added you as the ox-latex.el maintainer, assuming this is okay for
> Nicolas (Nicolas, let me know if I'm wrong.)
AFAIC, this is certainly okay.
Regards,
--
Nicolas Goaziou
ot; value))
>> ...
>> + ((string-match-p "^\\$" value)
>> ...
>> + ((string-match-p "^(" value)
>
> Why don't we just have an extra element property with the bracket info
> in the output of org-element-latex-fragment-parser?
Be
ffiliated keywords, which are here for
backward-compatibility reason, but shouldn't appear nowadays (and are
not even mentioned in the manual).
For the same reason, I suggest removing file+sys and file+emacs, which
were (and are AFAIK) planned for removal.
Regards,
--
Nicolas Goaziou
tion backend
> overriding default value derived from style.
In that situation, you can define a new style specific to the citation
back-end.
Regards,
--
Nicolas Goaziou
te{example1}. With two citations, the autocites command
> is followed by a relax command, such that the footnote incorrectly
> remains within the punctuation in the output pdf
> \autocites{example1}{example2}. Lorem ipsum dolor sit amet.
Regards,
--
Nicolas Goaziou
Hello,
"Bruce D'Arcus" writes:
> On Wed, Mar 23, 2022 at 5:27 PM Nicolas Goaziou
> wrote:
>> I can add it, but "full" is already the name of a variant, so
>> [cite/full: ...] and [cite/style/full: ...] would mean different things.
>> Is this
ould mean different things.
Is this a problem, or do you think of a better style name? Also, are
there possible variants for this style?
Regards,
--
Nicolas Goaziou
ave different packages targeting different needs, as
long as they share the same syntax.
Hopefully, at some point, we'll be able to build a list of blockers that
prevent Org Ref being built on top of Org Cite, and proceed.
Regards,
--
Nicolas Goaziou
Hello,
Ihor Radchenko writes:
> Nicolas Goaziou writes:
>
>> I think there should be a direct mapping between Customize interface and
>> values. Adding this macro as a band-aid to simply configuration is not,
>> IMO, a solution.
>
> I think that current custo
erefore cross-references might belong to an
extension instead.
> To assign additional properties, info "(org) Links in HTML export"
> https://orgmode.org/manual/Links-in-HTML-export.html recommends usage
> of "#+ATTR_HTML", but such technique has several issues:
This is a d
xt outside their
> allowed contexts (like quotes, source blocks, etc) as timestamps?
Allowing Org syntax in property values is creating another set of
problems: often the value is really a string that Org shouldn't try to
interpret.
Regards,
--
Nicolas Goaziou
, as a data
point, I find it very sad.
That's not helpful, tho.
Regards,
--
Nicolas Goaziou
not,
IMO, a solution.
If capture templates values are too complicated, what about simplifying
them, and possibly use this macro as a temporary solution to help
transition?
Regards,
--
Nicolas Goaziou
example demonstrating the issue? It should include
a minimal Org source, the LaTeX output, and the expected output.
Regards,
--
Nicolas Goaziou
ntax-table org-element--pair-square-table
> (ignore-errors (scan-lists (point) 1 0)))
> ...
>
> If there is an unbalanced double quote inside a bracket construction,
> that expression returns nil and not the position after the final
> bracket. But I don't know how to go on :-(.
I think I fixed it in bugfix branch. Thanks.
Regards,
--
Nicolas Goaziou
rather do it yourself, since it
> was your idea?
Please be my guest. :)
Regards,
--
Nicolas Goaziou
about using `write-region' instead of `write-file' and not touching
`set-auto-mode' function? Could you test it? Note the arguments are
different, the equivalent to (write-file file) would be (write-region
nil nil file).
Regards,
--
Nicolas Goaziou
Hello,
David Lukes writes:
> * lisp/oc-basic.el (org-cite-basic--parse-json): Make date-parsing and
> year extraction more resilient. Provide more informative errors when it
> fails.
Applied. Thanks.
Regards,
--
Nicolas Goaziou
nt: org-cite-processor,"
>
> Another question: if I would like to export to LaTeX but with citation
> commands rather than formated citations, would that be possible? I am sorry
> if I'm missing something obviuos.
Could you show an example of a source document and what you expect as an output?
Regards,
--
Nicolas Goaziou
Hello,
Jonas Bernoulli writes:
> ---
> etc/ORG-NEWS | 19 +++
Applied. Thank you.
Regards,
--
Nicolas Goaziou
Hello,
Juan Manuel Macías writes:
> I am attaching an updated version of the patch, which retrieves the
> `t' value for `:float' in tables and figures. The necessary information in
> the Manual is also updated.
Applied. Thank you.
Regards,
--
Nicolas Goaziou
ese changes -- if any -- seem acceptable, and
> whether they qualify as tinychange, and I'll happily submit a proper
> patch :)
All changes sound good. Please use `rx' for the regexp matching the
year.
This is a tinychange. I think this can be applied to the bugfix branch.
Thanks!
Regards,
--
Nicolas Goaziou
ot;standard" solution for that (aside from cloning the buffer and/or
> removing the restrictions)...
The "standard" solution is to use
Regards,
--
Nicolas Goaziou
-or-null-p" is better than ":safe t", even though but allowing
arbitrary locations (strings in this case) is not safe anyway.
Regards,
--
Nicolas Goaziou
atex--inline-image:
>
> ((string= float "t") 'figure)
>
> And in org-latex--decorate-table
>
> ((string= float "t") "table")
I think so.
Regards,
--
Nicolas Goaziou
ot tell if it
will suits you.
Regards,
--
Nicolas Goaziou
ited volumes?
Done in main branch. Please let me know if it works for you.
Regards,
--
Nicolas Goaziou
tences.
However, isn't it a bug? Shouldn't t value default to "figure"
environment, if only for the sake of backward compatibility?
Regards,
--
Nicolas Goaziou
gt; the above example I see:
>
> ┌
> │ Line Trust Warning
> │ 2 nil Missing definition for footnote [1]
> └
Fixed.
Thank you.
Regards,
--
Nicolas Goaziou
ure about the name of the
> variable as well.
Applied. Thank you! We can always revisit the variable name later.
Could you provides an ORG-NEWS entry for this?
Regards,
--
Nicolas Goaziou
Hello,
Samim Pezeshki writes:
> Thanks Nicolas for reviewing the changes!
>
> I applied the changes.
> Attached is the updated patch.
Applied. Thank you.
Regards,
--
Nicolas Goaziou
Hello,
Vincent Belaïche writes:
> Actually the source was in UTF-8,
Then use a zero-width space, and remove it from the output with
a filter.
Regards,
--
Nicolas Goaziou
n the source itself is not UTF-8?
I don't think there's a solution for you then, unless you convert it to
UTF-8, of course.
Regards,
--
Nicolas Goaziou
know this does not
> work this way.
You can put a zero-width space between ~ and /.
Regards,
--
Nicolas Goaziou
e last sentence is a left-over from the previous prototype.
> + (t
> + (org-element-set-contents
> + item (nconc
> + (mapcar (lambda (key) `(keyword (:key "KINDEX" :value ,key)))
> kindex)
> +(mapcar (lambda (cmd) `(keyword (:key "FINDEX" :value ,cmd)))
> findex)
> +(org-element-contents item
Indentation seems a bit off, otherwise, LGTM.
Regards,
--
Nicolas Goaziou
ine-items' at all. I.e., `org-texinfo-item' could
decide to prefix current tag with @itemx if 1) the item is empty 2) the
list has a non-nil :compact attribute 3) there's another item following
it. IOW, we do not need to rely on an :itemx property.
WDYT?
Regards,
--
Nicolas Goaziou
;)
> + (let ((case-fold-search nil))
> + (replace-regexp-in-string
> + org-texinfo--quoted-keys-regexp
AFAICT the variable is not defined in the patch.
Otherwise, LGTM.
Regards,
--
Nicolas Goaziou
Hello,
Rudolf Adamkovič writes:
> The =org-mode-flyspell-verify= function should skip over citations.
>
> For example, the following citation get flagged as misspelled:
>
> [cite:@ganz+2013]
Fixed. Thank you.
Regards,
--
Nicolas Goaziou
sion 1.16.0)
> of 2020-09-19
> Package: Org mode version 9.4.6 (9.4.6-g069bcb @
> /home/msi/.emacs.d/straight/build/org/)
IIRC, it was fixed in Org 9.5.1. You may want to update Org.
Regards,
--
Nicolas Goaziou
Maybe:
(insert (propertize org-agenda-clock-report-header 'face
'org-agenda-structure))
Could you send an updated patch?
Regards,
--
Nicolas Goaziou
(let ((author (org-cite-basic--get-field 'author key info)))
> + (let ((author (org-cite-basic--get-field 'author key info
> 'raw)))
Why do you think the optional argument is needed here?
Regards,
--
Nicolas Goaziou
]]
>
> which does not render.
Note that Org Cite and Org Ref are, unfortunately, incompatible
projects. Org Cite defines citations as a new kind of object, whereas
Org Ref extends links to create citations. In short, you cannot mix
both.
Regards,
--
Nicolas Goaziou
use
(org-element-interpret-data (org-element-contents special-block))
Regards,
--
Nicolas Goaziou
ists with such an
attribute, for the same result:
#+attr_texinfo: :compact t
- key: a ::
- key: b ::
#+attr_texinfo: :compact t
- key: c ::
- key: d ::
- This is a regular list since it does not have :compact attribute.
IIRC, I did an experiment like this one when introducing matrices in
LaTeX export.
Regards,
--
Nicolas Goaziou
`raw');
> to me that seems appropriate too.
I think that's abusing export snippets. They are more user-oriented,
e.g. filters can apply to them.
Note you can write (org-export-raw-string (some-public-function "C-c
SPC")) where (some-public-function "C-c SPC") => "@kbd{C-c @key{SPC}}",
as done currently by the "kbd" macro.
Regards,
--
Nicolas Goaziou
ndex and kindex entries to
> +its content. If the bullet is \"+\" then use \"@itemx\" and deal with
> +data from preceeding siblings that use such a bullet."
> + (let (key cmd)
> +(if (string-match " +(\\([^()]+\\)) *\\'" args)
Could you use `rx' here?
> +(setq key (substring args 0 (match-beginning 0))
> + cmd (match-string 1 args))
> + (setq key args))
> +(org-element-put-property
> + item :tag
> + (nconc (if (assoc "kbd" org-macro-templates)
> +(let ((templates org-macro-templates))
> + (with-temp-buffer
> +(insert (format "{{{kbd(%s)}}}" key))
Here, there could be a function building the key chord, and you could
wrap the result into a raw string (see `org-export-raw-string').
Regards,
--
Nicolas Goaziou
item (pop contents))
> +(let ((next-item (car contents)))
> + (when (and next-item
> + (equal (org-element-property :bullet next-item) "+
> "))
The above will fail if `org-list-two-spaces-after-bullet-regexp' is
non-nil. You should compare the trimmed bullet with "+".
Anyhow, relying on mixed bullets is not great…
Regards,
--
Nicolas Goaziou
'string)
> +
> +
> +(defcustom org-icalendar-deadline-summary-prepend "DL: "
> + "String used for prepending summary in exported deadlines."
> + :group 'org-export-icalendar
> + :type 'string)
> +
Could you add missing :safe and :package-version keywords?
Regards,
--
Nicolas Goaziou
(if (zerop alarm-time)
> + org-icalendar-alarm-time
> + alarm-time))
I suggest to refactor the above into something like:
(cond
((> alarm-time 0) alarm-time)
((and (= 0 alarm-time) org-icalendar-force-alarm) alarm-time)
(t org-icalendar-alarm-time))
Could you send an updated patch?
Regards,
--
Nicolas Goaziou
Hello,
Ihor Radchenko writes:
> Nicolas,
> Let me know if I miss something about special block parsing.
LGTM! Thanks.
Regards,
--
Nicolas Goaziou
"Thomas S. Dye" writes:
> IIUC, the map in 'org-cite-biblatex-styles' is correct for
> biblatex-chicago.
biblatex-chicago introduces new LaTeX commands. Does that mean those can
be ignored?
Regards,
"Thomas S. Dye" writes:
> Hmm, I can't find 'org-cite-biblatex-styles' in main.
>
> Do you mean the map represented by the nested pcase in
> org-cite-biblatex-export-citation function, or something else?
You need to update main. `org-cite-biblatex-styles' is a recent addition
to oc-biblatex.el.
Hello,
"Thomas S. Dye" writes:
> Nicolas Goaziou writes:
>
>> Another possibility it to write, e.g., "oc-biblatex-chicago.el" and
>> define a new ‘biblatex-chicago’ export processor, re-using most
>> functions from "oc-biblatex.el". It wo
it? The machine I am on right now does not
> allow external ssh access.
Unfortunately, this seems to break "test-org/auto-fill-function" test.
Could you have a look at it?
Regards,
--
Nicolas Goaziou
nsuccessfull, fail.
>
> BTW : my current code does *not* work, and I do not understand why my
> test used to succeed... A better patch will follow ( but not
> tonight...).
Since you are probably busy, I implemented this on your behalf. The new
behaviour is in main branch. Thank you.
Regards,
--
Nicolas Goaziou
ost
functions from "oc-biblatex.el". It would probably only be necessary to
re-define ‘org-cite-biblatex-export-citation’ and
‘org-cite-biblatex-prepare-preamble’.
WDYT?
Regards,
--
Nicolas Goaziou
gt; compilation.
OK. I applied your patch and modified some docstrings accordingly. Thank
you.
Regards,
--
Nicolas Goaziou
Binding the command to (kbd "C-c C-") instead works, but not on a
> tty.
>
> It's been my understanding that "TAB" is the ascii control character,
> identical to C-i, and hence "C-TAB" cannot work. "" is the GUI
> system's key event (in my case, X), and does not work on a terminal.
Fixed.
Thank you.
Regards,
--
Nicolas Goaziou
aybe we should spell out the
"empty value" part of the prompt.
Regards,
--
Nicolas Goaziou
Hello,
Ihor Radchenko writes:
> Nicolas Goaziou writes:
>> But then, you do not remove the ambiguity that is condemned in this
>> thread. The greater element/element and greater element/lesser element
>> distinctions are equivalent, albeit not identical.
>
> AFAIU,
e binding. You could test
(call-interactively o-c-l-b-f) instead.
Besides, tests are not a blocker.
Regards,
--
Nicolas Goaziou
n from 4.5s to 1.5s. I am using
Emacs 27.2.
Regards,
--
Nicolas Goaziou
12sec!
Fixed. Thank you.
Regards,
--
Nicolas Goaziou
Ihor Radchenko writes:
>> There are actually three types of elements: not all elements can contain
>> objects.
>
> You are right. However, I am not sure if it is a good idea to mention
> this in the introduction part of the syntax document.
>
> Maybe we can just say "... lesser elements" that can
main categories are used to classify these environments:
> "elements" and "objects", from the broadest scope to the narrowest.
> "Elements" consist of "greater elements" that can contain other
> elements and objects and "lesser elements&qu
posal.
Besides, they already part of the syntax, in some way. So that ship has
sailed long ago.
Regards,
--
Nicolas Goaziou
doesn't
change current syntax, which is a big advantage.
Regards,
--
Nicolas Goaziou
t;~/Projekte/csl.styles/", you
could use:
(setq org-cite-csl-styles-dir "~/Projekte/csl.styles/")
In that case, the second token from "cite_export" keyword would become:
#+cite_export: csl chicago-author-date.csl
Note there is no "csl_style" keyword in Org Cite. It might be related to
Org Ref, which is a different citation system.
HTH,
--
Nicolas Goaziou
. J/o”urnal of Plain Text Formats/ 42
(1).
--8<---cut here---end--->8---
I tested with development Org, but I don't think it would change using
stable Org. Maybe someone wants to confirm this.
Regards,
--
Nicolas Goaziou
d by whitespace. Neither are =KEYPREFIX=, =@KEY=, or =KEYSUFFIX=
> separated by whitespace.
Addendum: whitespaces are not significant after the leading colon, and
before the closing square bracket. They are significant in any other
case.
HTH,
Regards,
--
Nicolas Goaziou
this function probably wasn't meant to be
public in the first place. Now it is.
> So would this patch work?
Such a patch must be accompanied with tests.
Regards,
--
Nicolas Goaziou
nclined to
> think this would be a good change in terms of user experience.
OK. I implemented this on main branch. We'll see how it goes.
Thanks.
Regards,
--
Nicolas Goaziou
ryone whenever Org
is loaded. This may not be what you have in mind.
Regards,
--
Nicolas Goaziou
le)
> + (run-hook-with-args 'org-icalendar-after-save-hook file) nil
This is not really the same fix. You're quoting a lambda, which should
not be required if the problem disappeared. IOW, the true fix probably
belong in the `org-export-async-start' function.
WDYT?
Regards,
--
Nicolas Goaziou
Hello,
"Bruce D'Arcus" writes:
> Is there any reason not to autoload the processors?
I am not sure about what you mean. Could you elaborate?
Regards,
--
Nicolas Goaziou
to be the new standard:
> <2021-11-27 Sat 10:30>--<2021-11-27 Sat 12:30>
Both are valid. Maybe the manual needs some clarification. Would you
want to tackle it?
Regards,
--
Nicolas Goaziou
ix it.
Applied. Thank you.
> I don’t really understand why this bug happens to be honest.
The patch is already an improvement, but the beast is still lurking,
indeed.
Regards,
--
Nicolas Goaziou
re if it is the
> best fix, though...
IMO, this is a bit of a kludge.
"oc.el" parses language-region tags already, although it has not been
factored out as an independent function yet. See
`org-cite--get-note-rule'. Maybe moving this part to "org-macs.el" would
be a be
-cite-export-processors' instead, e.g., to
((t biblatex "chicago-authordate"))
You are responsible, however, for requiring appropriate packages in the
document header (with `org-latex-packages-alist', for example).
Regards,
--
Nicolas Goaziou
w how Org does it. This is just a red herring. What is useful,
however, is to fontify them the way Org sees them.
Regards,
--
Nicolas Goaziou
o it is invalid, both are then highlighted.
>
> Can you reproduce that?
I reproduced it on a fresh Emacs. IIUC, it stemmed from the fact that
fontification required "ox.el" to be loaded beforehand.
It should now be fixed. Thanks.
Regards,
--
Nicolas Goaziou
-map, org-element-parse-buffer, org-element-cache, and
> jit-lock-mode. Each type of Org element/object can be assigned with a
> fontification function accepting a single argument - the element datum.
>
> Also, the fontification code can be move to a separate library.
>
> WDYT?
I wholeheartedly agree with all these points.
Regards,
--
Nicolas Goaziou
tar/discussions/430#discussioncomment-1693707
>
> Can anyone else confirm this?
I couldn't reproduce it, but I saw something fishy in the fontification
code. I fixed it. Hopefully, your problem is gone, too. Crossing
fingers.
Regards,
--
Nicolas Goaziou
itself,
> +the result may be unsettling. For example,
> +
> +#+begin_example
> +/One may expect this whole sentence to be italicized, but the
> +following ~user/?variable~ contains =/= character, which effectively
> +stops emphasis there./
> +#+end_example
> +
> +You can use zero width space to help Org sorting out the ambiguity.
> +See [[*Escape Character]] for more details.
LGTM!
Regards,
--
Nicolas Goaziou
o longer
> go
> over the maximum length :)
`line-number-display-width' is Emacs 26+. So I guess it is unfortunately
not acceptable on main branch.
Regards,
--
Nicolas Goaziou
the "Item" section.
I see no reason to change the prefix, since these functions are part of
ox-texinfo. I didn't look closely at your code, tho, so I may be wide of
the mark.
WDYT?
Regards,
--
Nicolas Goaziou
the last stable version. I.e., we don't need to delay
artificially the release (but we may delay this one for other reasons,
obviously).
WDYT?
Regards,
--
Nicolas Goaziou
Hello,
Bastien writes:
> Ihor Radchenko writes:
>
>> Bastien, should we package Org 9.5 to Org ELPA?
>
> Done, thanks a lot for the heads up!
While we're at it… maybe a 9.5.1 release is in order? Just sayin'…
Regards,
--
Nicolas Goaziou
Hello,
"Bruce D'Arcus" writes:
> Subject: [PATCH] oc-basic: Add function to shorten names
>
> * lisp/oc-basic.el (org-cite-basic--shorten-names): new function to
> shorten author names
Applied. Thank you.
Regards,
--
Nicolas Goaziou
g *10*.0!
So, I'm not totally convinced it is worth the trouble.
Regards,
--
Nicolas Goaziou
se an absolute file name.
I think a better order for a relative file name would be:
1. relatively to `org-cite-csl-styles-dir',
2. relatively to buffer's default directory,
3. failure.
WDYT?
Regards,
--
Nicolas Goaziou
info+.el
> style for most or all definitions but use the additional flexibility of
> ox-texinfo.el, when that is needed.
How is it possible? Keywords are global. How do you change value
locally?
Regards,
--
Nicolas Goaziou
then apply all fontification
functions to the resulting tree rather than have each of them calling
the parser, like the above.
In any case, I think fontification deserves a dedicated thread, in
addition to some love.
Regards,
--
Nicolas Goaziou
of this thread :
> https://lists.gnu.org/archive/html/emacs-orgmode/2013-04/msg01478.html
Fixed.
Thank you.
Regards,
--
Nicolas Goaziou
t; (group ,mark)
>>> (or (any space ?- ?. ?, ?\; ?: ?! ?? ?' ?\" ?\) ?\} ?\\ ?\[)
>>> line-end))
I don't think it is necessary. /word/? seems a valid sentence closing.
Regards,
--
Nicolas Goaziou
1 - 100 of 9824 matches
Mail list logo
