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
does not recognize styles. It is up to
the processor to interpret it as a short-hand for "suppress-author".
Regards,
--
Nicolas Goaziou
) because Org does not move space around footnotes.
It does not sound to bad, tho.
Regards,
--
Nicolas Goaziou
; citations, I would expect no problem here.
Indeed, there is no problem above. The discussion is about emphasis
within prefix or suffix.
Regards,
--
Nicolas Goaziou
Hello,
"Bruce D'Arcus" writes:
> Nicolas,
>
> Quick syntax question:
>
> On Wed, Apr 21, 2021 at 7:34 PM Nicolas Goaziou
> wrote:
>
>> As a reminder, the full citation syntax is
>>
>> [cite/style:common prefix ;prefix -@key suffix; ... ; com
order
to eventually make an informed choice.
Regards,
--
Nicolas Goaziou
Nicolas Goaziou writes:
> "Bruce D'Arcus" writes:
>
>> In general (conceptually), if you have one footnote in text, and one
>> in a footnote, with a note style, both will be rendered as footnotes.
>>
>> So in an adapted version from earlier:
>>
Tim Visher writes:
> Thanks for the tip. What I'm thinking more is somehow getting the heading
> pre-output generation, stripping any characters that `org` would consider
> special (I'm hoping there's already a function that can at least mark
> 'markup' text in a given org string), and _then_
ld markup, but what would happen to, e.g., a_b or \alpha
or <>?
HTH,
--
Nicolas Goaziou
(equal '(0 3 7 8 9 10 11)
> + (funcall list-visible-lines 'ancestors-full t)))
> +(should (equal '(0 3 7 8 9 10 11)
> + (funcall list-visible-lines 'ancestors-full nil)))
Are you sure you want to display line 10? No other visibility does that.
Regards,
--
Nicolas Goaziou
; 28) only flickers briefly, so I can't actually see it.
It works here when I enable `tooltip-mode'.
Regards,
--
Nicolas Goaziou
macro.el".
However, as a start, I suggest starting a new thread about a suggested
change in the syntax, with a clear title, examples, and code. Then we
can leave time for users to react to it.
Do you want to take care of it?
Regards,
--
Nicolas Goaziou
also go low-tech and call `eval-buffer' on "org-element.el",
"oc.el", "org-element.el", "ox.el" and "org.el".
This should be enough for testing.
Regards,
--
Nicolas Goaziou
;oc.el", for example
(defun org-cite-wrap-footnote (citation)
"Wrap CITATION object within an anonymous footnote."
...)
which can be used upon "exporting" the footnote, after having done
appropriate checks.
Regards,
--
Nicolas Goaziou
uire
a more specific tool.
Do you have a small example (org + desired output) so I can experiment
with it?
Regards,
--
Nicolas Goaziou
te-register-processor 'demo
:activate #'org-cite-demo-activate
:export-citation #'org-cite-demo-export-citation
:export-finalizer #'org-cite-demo-finalizer)
That's about it.
You can, if you wish so, try out this demo on the following document:
--8<---cut here---start->8---
#+cite_export: demo
#+bibliography: bib.bib
#+bibliography: bib2.bib
Simple reference: [cite:@key]
Multiple references: [cite:@key1;@key2]
Suppress author: [cite:-@key]
Plain style: [cite/plain:@key]
Full syntax: [cite:common prefix ;prefix @key suffix ;@key2; common suffix]
#+print_bibliography:
# Local Variables:
# org-cite-activate-processor: demo
# End:
--8<---cut here---end--->8---
WDYT?
Regards,
--
Nicolas Goaziou
Also, if all goes well, there will be a need for a complete
documentation in the manual… Hear, hear.
Regards,
--
Nicolas Goaziou
s a detail of implementation. We
current only cache, and freeze, ID actually being referred to, but that
could be extended.
I'd link to make sure everyone understands the problems that the current
implementation is trying to solve before throwing it out of the window.
Regards,
--
Nicolas Goaziou
exported (i.e., one off documents), this is not so an issue (IMO)
since you have custom ID. I assume this was evoked in the thread.
Link stability is also tied to publishing process because it needs
a cache. And I lazily re-used the cache already implemented there.
Regards,
--
Nicolas Goaziou
k-run 1 (org-sort-list t ?a))
>
> in a file (1100 lines) obtained using
I don't think performance is really an issue. Of course, the suggested
function is clearly slower than the current one.
Regards,
--
Nicolas Goaziou
modified tree.
tree)))
--8<---cut here---end--->8---
> 2. Missed spaces
>
> #+begin_src elisp
> (org-sort-remove-invisible "A *b* /i/ t.")
> #+end_src
>
> #+RESULTS:
> : A bit.
You need to update Org. I added a fix for that in "org-element"
yesterday.
Regards,
--
Nicolas Goaziou
ld. So-called "compact" form was introduced after the
others.
Regards,
--
Nicolas Goaziou
(and (not sep)
> (if (save-excursion
> (not (re-search-forward (nth 1 tmp) end t)))
> (setq sep (nth 0 tmp))
> (setq sep-rexp (cdr sep-rexp))
> (setq tmp (car sep-rexp)
I suggest this (yes, I like pattern-matching, `car' and `cdr' are so
80's) instead:
(save-excursion
(goto-char beg)
(catch :found
(pcase-dolist (`(,sep ,regexp) sep-regexp)
(save-excursion
(unless (re-search-forward regexp end t)
(throw :found sep
nil))
Again all this needs to extensively tested, as there are a lot of
dangers lurking around.
Regards,
--
Nicolas Goaziou
each entry one by one to expand, it would be
> very repetitive. I think this is helpful for generating HTML page or
> PDF from matching query quickly.
OK. Then what about a shorter `ancestors-full'?
Also, could you provide tests for it in `test-org/show-set-visibility'?
Regards,
--
Nicolas Goaziou
h.
Note that I merely answered your questions in the initial post. I didn't
try to solve a problem you weren't formulating anyway.
I don't know what "tec's fix" is, but if you found a solution, that's
great!
Regards,
--
Nicolas Goaziou
rences are appropriately set.
If you later want to refer to the table, you can write, e.g.,
#+name: t1
#+begin_src R :exports both
library(tidyverse)
x <- tribble(~a, ~b, 1, 3)
x
#+end_src
#+name: t1_output
#+caption: Org Table
#+results: t1
| 1 | 3 |
so [[t1_output]] links jump to the table.
HTH,
--
Nicolas Goaziou
Maxim Nikulin writes:
> On 19/04/2021 23:08, Nicolas Goaziou wrote:
>>> + ;; Space role in sorting.
>>> + ;; Test would fail for locales with ignored space, e.g. en_US, it
>>> works
>>> + ;; in C and currently rare locales havi
e.
In this case, you are referencing the source code block whereas you want
to reference the table. So #+name should go before the table.
Note that if you follow [[t1]] link, point will move to the source code
block, not the table.
Regards,
--
Nicolas Goaziou
dolist (case '(("Lost =in *verbatim* text= fragment" .
> + "Lost in *verbatim* text fragment")
> + ("Adjucent emphasis: *Overlapped* /regexps/" .
> + "Adjucent emphasis: Ovelapped regexps")))
typo
Regards,
--
Nicolas Goaziou
is significant.
See (info "(texinfo)Node Line Requirements").
Apparently, any case combination from "Top" is forbidden. But this is
not documented in the Texinfo manual.
I worked around it, but I suggest to report it upstream, too.
Fixed. Thanks.
Regards,
--
Nicolas Goaziou
. Is it possible to circumvent this limitation?
Regards,
--
Nicolas Goaziou
Hello,
Maxim Nikulin writes:
> On 05/04/2021 06:06, Nicolas Goaziou wrote:
>> Joost Kremers writes:
>>
>>> I tend to agree that allowing local modifications of Org's syntax is pretty
>>> much
>>> pointless, but then why is `org-emphasis-alist` a u
t of replacement
macros use case. IMO, macros are good for short text. For bigger ones,
you may want to use some Babel code, in the language of your choice.
WDYT?
Regards,
--
Nicolas Goaziou
g-verbatim-re remove-markers
(replace-regexp-in-string org-emph-re remove-markers
(org-link-display-format s) t tt)
t t)))
--8<---cut here---end------->8---
Regards,
--
Nicolas Goaziou
ting documentations, so I wish to have some feedbacks before moving
> on. Is there better way to achieve this effect? Am I overlooking
> something?
Don't you need to simply move point within the entry and use `ancestors'
view?
Regards,
--
Nicolas Goaziou
TAB, assume TAB-separated material
> - - when each line contains a comma, assume CSV material
> - - else, assume one or more SPACE characters as separator."
> + separator using `org-table-guess-seperator'."
I wonder if creating a new function is warranted here. You could add the
news checks after those already present in the code, couldn't you?
Regards,
--
Nicolas Goaziou
:table-of-contents is not a valid option; use
> :with-toc instead. :publishing-function is required.
Applied. Thank you.
Regards,
--
Nicolas Goaziou
e containing a citation” should probably return nil.
Indeed. If there is no footnote definition containing the citation, it
returns nil.
Regards,
--
Nicolas Goaziou
auto-generated
>> label:
>
> Confirmed with org from git a few minutes ago. The link using an
> auto-generated label would be fine if the label were the one for the
> special block but it's not.
I couldn't reproduce it.
Regards,
--
Nicolas Goaziou
there is CSL-JSON and a CSL-YAML etc. If different "display"
> and "follow" processors will be able to handle different formats then
> the users might want to change those settings locally as well, based
> on the bibliography format, but I'm not sure what kind of
> infrastructure would be the best way of supporting this. (E.g.,
> registering format support information about the processors and
> choosing on this basis?)
I don't have an idea about it either. This is not a blocker, tho. We can
revisit it later, once we have "something" working.
Thanks for your feedback.
Regards,
--
Nicolas Goaziou
I added a rough export for doi links in master. I hope this fixes your
issue.
Regards,
--
Nicolas Goaziou
if you add a section?
These links should be stable in a publishing context (i.e., you use
`org-publish' to generate the document), even if you add a section.
Regards,
--
Nicolas Goaziou
rt-link', fontification, export?
> *heading to be linked to
>
> Actual rendered result
>
> **heading to be linked to
If you're talking about `org-insert-link', this is not a bug. The first
star is a special markup indicating you're specifically linking to
a headline.
Regards,
--
Nicolas Goaziou
free software project (not counting wiki edits),
> so I hope I got everything right.
It was almost perfect! ;) I only added a line in the commit message
about the section of the manual being fixed.
Regards,
--
Nicolas Goaziou
Hello,
Stefan Monnier writes:
> I just saw that it burps in Emacs-26 because of a bug when functions are
> declared with 0 optional arguments like ( x).
>
> So I suggest the patch below,
Applied. Thank you.
Regards,
--
Nicolas Goaziou
is broke our internal
macros (e.g., {{{n}}} and {{{property}}}) so I updated them.
I mentioned it in the ORG-NEWS file, and applied your changes. We'll see
how it goes.
Regards,
--
Nicolas Goaziou
{
Here, it should be #+kindex: C-@{
> #+kindex: C-}
Ditto.
Regards,
--
Nicolas Goaziou
Hello,
Ramesh Nedunchezian writes:
> See the attached files. Export works fine with html and odt, btw.
Fixed. Thank you.
Regards,
--
Nicolas Goaziou
-export-expand-include-keyword' from
`org-babel-pre-tangle-hook'. Untested.
Regards,
--
Nicolas Goaziou
ill be a backend issue if these backends
> share code.
Fixed. Thank you.
Regards,
--
Nicolas Goaziou
Hello,
"Bruce D'Arcus" writes:
> Maybe since Nicolas has been around lately, he can weigh in?
I guess I can make a summary about the current state of the citations
branch, i.e., what is done, what is missing.
There are three major steps to complete in order to add citations in
n of
salt.
Regards,
--
Nicolas Goaziou
Hello,
Ramesh Nedunchezian writes:
> In the attached files, there are links pointing to itemized headlines
> ... and the problem is the items have no anchors associated with it.
Fixed. Thank you.
Regards,
--
Nicolas Goaziou
lists causes no issue:
- b
- *a*
and
- *b*
- a
Regards,
--
Nicolas Goaziou
se this very simple patch to fix that problem.
Thank you.
Could you apply the same fix to the `org-verbatim-re' match above, and
provide an appropriate commit message?
Regards,
--
Nicolas Goaziou
nvinced this should be configurable, as I fail to see
a use-case for such a customization. Note that in the case you mention,
comment syntax should probably be part of the coderef label itself.
Regards,
--
Nicolas Goaziou
vel 4.
Anyway, this should be fixed. Thank you.
Regards,
--
Nicolas Goaziou
polish and push
yet.
Regards,
--
Nicolas Goaziou
ch so Org users can
test it.
WDYT?
Regards,
--
Nicolas Goaziou
e-single-block and provides a
> standard way to specify a :coderef-prefix regexp so that empty
> comments can be stripped.
Would you mind answering my questions first? I still don't follow you
about the coderef prefix/regexp.
Regards,
--
Nicolas Goaziou
M |
|---+--|
| Goal 3| 1:00 |
|---+--|
| Task 1| 1:00 |
|---+--|
| Subtask 1 | 1:00 |
This looks wrong.
Regards,
--
Nicolas Goaziou
Hello,
Adam Sneller writes:
> Nicholas - can you recommend how to best implement this with
> font-lock-add-keywords?
I think you can add a function as a matcher. The function could probably
be what you wrote already.
See `org-set-font-lock-defaults' for examples.
Regards,
--
Nicolas Goaziou
ernal link types, as writing [[fuzzy:whatever]] would be
confusing for Org. As a consequence, link parameters are not meant to
control internal links.
We might need a different variable specific to internal links, but in
the current case, using `font-lock-add-keywords' should be sufficient.
Regards,
--
Nicolas Goaziou
lace-regexp-in-string: Wrong type argument: arrayp, nil
>
> Thanks for reporting. The failure was introduced by bcfe6f985
> (ox-latex: convert verbatim text in headings to texttt, 2021-04-04).
> The below change seems to fix the issue, though Nicolas may be able to
> suggest a
both cases"? In particular, what is
a coderef regexp in this context? I know about coderef format, but
I don't think users are supposed to provide a regexp here.
Regards,
--
Nicolas Goaziou
that goal.
>
> I tend to agree that allowing local modifications of Org's syntax is pretty
> much
> pointless, but then why is `org-emphasis-alist` a user option?
In practice, the faces, i.e., the values, are meant to be customizable,
not the keys.
Regards,
--
Nicolas Goaziou
needs now and into the
> future?
I think you misunderstood me. I'm not against Org syntax evolving
somehow if necessary, but I see no good in users cooking their own pet
Org syntax. IMO, Markdown syntax is an example not to follow. Therefore,
I would not recommend digging in that direction.
Regards,
by `org-element-parse-buffer`, it should be easier to modify the
> front-end syntax.
I think they do.
Anyway, one of the goals of Org is to provide a universal document
format. It is not there yet, but allowing local modifications of the
syntax certainly goes against that goal.
Regards,
--
Nicolas Goaziou
Ramesh Nedunchezian writes:
> The advantage is you move to an error, fix it, then M-g M-n, fix it
> and so on and so forth.
But all reports are not errors. You may not want to fix them all either.
OTOH, you lose the ability to hide or ignore unwanted reports, or sort
them by trust level.
I
ource buffer or
> the linter report?
You move back to the linter report and proceed from there. I cannot
think of any other way.
Regards,
--
Nicolas Goaziou
information).
This is not the appropriate location for the fix.
In `section-back-end' variable within `org-latex-headline', you can
extend the local export back-end to handle correctly verbatim markup.
Regards,
--
Nicolas Goaziou
Ramesh Nedunchezian writes:
> While in the lint buffer, I was expecting that M-g M-n, M-g M-p would
> take me to the relevant source lines. Unfortunately, this isn't the
> case. And the linter report is derived from
> `org-lint--report-mode-map' which is derived from
> `tabulated-list-mode'.
g are the lines that seem relevant to the problem at hand.
No, this is a different issue. We're talking about the first part of
a menu entry, which doesn't have the same limitations as a node name.
Those limitations are not explicit in the Texinfo manual, AFAICT.
Regards,
--
Nicolas Goaziou
e standard header arguments like everything else so that
> users can migrate away from switches with an eye toward removing them
> entirely.
Switches predate Babel and its header arguments. Also, they are
orthogonal to Babel. I don't know what a sound design would be here,
tho.
Regards,
--
Nicolas Goaziou
o}. IOW, you need a fourth pair of braces in this case.
Regards,
--
Nicolas Goaziou
Hello,
Ramesh Nedunchezian writes:
> When I export the following snippet to TexInfo format the export fails.
>
>
> ** To add a package: (submission, submit)
>
> Adding a basic package is very simple. There are thorough
This should now be fixed. Thank you.
Regards,
--
Nicolas Goaziou
t; as a link. I guess, it should not happen.
Actually, this is (was?) intentional. By forbidding parenthesis in
a plain URL, you allow one to type, e.g., (https://orgmode.org), which
is, IMO, a more frequent need than having to deal with parenthesis in
the URL.
Regards,
--
Nicolas Goaziou
omes the title of the
document, i.e., the document becomes morally equivalent to:
#+title: test
<2021-03-18 Thu 15:00-16:00>
body of text
There is indeed no event to export in this case. Only level 2 outline
will become events. You may want to export region instead.
Regards,
--
Nicolas Goaziou
gt; last line of table.el table ending in "--+".
Oops. Fixed. Thank you.
Regards,
--
Nicolas Goaziou
Hello,
stardiviner writes:
> Bump this thread, hi, Nicolas, any thoughts or update about this?
>
> stardiviner writes:
>
>> I have following minimal testing code:
>>
>> #+begin_src emacs-lisp
>> (defun org-link-beautify (start end path bracketp)
>
e---end--->8---
[...]
> Evaluating `(org-element-at-point)' returns `(paragraph ...)' all along
> the top line and `(table ( :type org ))' when the cursor is at
> the beginning of the `a b c' line.
Fixed. Thank you.
Regards,
--
Nicolas Goaziou
keywords and macros are expanded*
> and Babel code blocks executed, on a copy of the original buffer
> being exported. Visibility and narrowing are preserved. Point
> is at the beginning of the buffer.
There is also `org-export-before-parsing-hook'.
Regards,
--
Nicolas Goaziou
fixed in master branch. Let me knows if it works for
you.
Thank you for the report.
Regards,
--
Nicolas Goaziou
Ken Mankoff writes:
> Yes, I meant to write that I think Org syntax is maybe *not*
> context-free, and therefore EBNF can't capture all of it. But it could
> still be very helpful and capture most of it.
I'm not arguing about the usefulness of a partial EBNF description. I'm
merely pointing out
Hello,
Ken Mankoff writes:
> I question if this is possible because EBNF is for context-free
> grammars, but I *think* Org syntax is context-free.
It's not as explained in a footnote in the Org syntax document.
Regards,
--
Nicolas Goaziou
Uppercase is used in the manual as
a poor man's bold, and supported for historical reasons.
Regards,
--
Nicolas Goaziou
get the results from the block.
"Include" is an export-only directive, which is not the case
of :exports. They live in two different worlds, and I think it is a good
thing to keep them orthogonal.
You may be looking after Babel calls.
Regards,
--
Nicolas Goaziou
nerated file, that
>> shouldn't be necessary.
>>
>> Is there a way to turn that off and just have it overwrite the file?
>
> Anyone seeing this?
No. Could you M-x toggle-degug-on-quit, reproduce it, C-g when you're
asked about updating the file, and send the backtrace?
Regards,
--
Nicolas Goaziou
ted by another buffer.
>
> Is this desired behavior?
It depends. If MARKERP is non-nil, you certainly don't want to close the
newly created buffer. Otherwise, it could be closed, indeed.
I patched master along these lines. Thank you.
Regards,
--
Nicolas Goaziou
re is one already. You may want to
use another option if you want to replace results.
Regards,
--
Nicolas Goaziou
capture templates, which are left
as-is, i.e. a "final newline" is not added in that case.
I don't know if that answers your question, but HTH.
Regards,
--
Nicolas Goaziou
u ante vel est convallis dignissim. Fusce
> suscipit, wisi nec facilisis facilisis, est dui
> fermentum - Some text, indented
I just released orgalist 1.13, which should fix this problem. Please let
me know how it goes. You need to wait for GNU ELPA to catch up, tho.
Regards,
--
Nicolas Goaziou
Hello,
Ihor Radchenko writes:
> Subject: [PATCH] Fix `org-lint-link-to-local-file'.
Applied. Thank you.
Regards,
--
Nicolas Goaziou
nothing."
Just let them go.
Regards,
--
Nicolas Goaziou
t;, "Install", ..., are
useful. Worse, I have some feeling they could give a wrong impression
about the software.
It doesn't look bad, BTW.
Regards,
--
Nicolas Goaziou
Hello,
Ypo writes:
> Thanks. It seems the problem is that "file:" links have changed their
> behaviour. They must be replaced by "file+sys:" links. In this way,
> folders are open in Windows OS.
file+sys: links are deprecated, tho.
I suggest to not use them.
Regards,
--
Nicolas Goaziou
for raw LaTeX in a document.
This is not AucTeX. For specific needs, you may want to use LaTeX
blocks, i.e., #+begin_export latex...
Regards,
--
Nicolas Goaziou
s in org.el).
> The attached patch fixes the original issue.
Thank you. I applied your patch.
Regards,
--
Nicolas Goaziou
401 - 500 of 10107 matches
Mail list logo
