blank
This looks wrong, but so does the current regexp. It should not be
`space' nor `blank', but [ \t] per Org syntax.
Regards,
--
Nicolas Goaziou
hedule them, or add a note, as long as
`org-at-encrypted-entry-p' is non-nil. I don't think you can handle the
initial problem otherwise.
Regards,
--
Nicolas Goaziou
bly a generic solution, but do we really need one? If you
want to access programmatically to notes, don't set
`org-log-into-drawer' to nil.
Regards,
--
Nicolas Goaziou
--->8---
Since such data is never needed for encryption, I suggest to stay on the
safe side and encrypt anything below the properties drawer.
Regards,
--
Nicolas Goaziou
cut here---end--->8---
Upon saving the file, I type the key twice, and the entry is encrypted.
Note that I evaluated (org-crypt-use-before-save-magic) once beforehand.
Regards,
--
Nicolas Goaziou
r links like this "[[#AB", the editor will assume that
> the link is completed by the close brackets of the next link, thus,
> combining the two links into one. I have to carefully delete the
> beginning brackets or ending brackets to allow me to fix things.
IIRC, this is already fixed i
-g9f0af6 @
/home/nicolas/.config/emacs/straight/build/org-plus-contrib/)
--
Nicolas De Jaeghere
Hello,
Bastien writes:
> akater writes:
>
>> We replace some repetetive code with macro calls org-prog-plist and
>> org-let*-prog-plist.
>
> IIUC this is a refactoring, it does not add or remove functionalities?
>
> I'll let Nicolas decide on this, of course.
F
t. It doesn't seem to be a big deal, however,
as you don't lose anything by keeping notes in old syntax around.
Regards,
--
Nicolas Goaziou
y `org-latex-prefer-user-labels' has a nil default
value.
The following patch implements the same for HTML. I didn't test it
thoroughly, tho.
Regards,
--
Nicolas Goaziou
>From 243c213c205b8157d9ce5552dd0489cc6ae229ff Mon Sep 17 00:00:00 2001
From: Nicolas Goaziou
Date: Tue, 8 Sep 2020
)
> + (throw :found
> + (org-element-property
> + :value element))))))
See `org-collect-keywords'.
Regards,
--
Nicolas Goaziou
Hello,
Bastien writes:
> There is none, that's indeed a backward compatibility issue.
Note that exporting to a different directory is called publishing.
Regards,
--
Nicolas Goaziou
ng a line with an asterisk
followed by a space _always_ create a headline. However, writing an item
with a line break at the end of its first line is not necessarily
a note.
- Question.\\
Why would this be a note?
- Answer.\\
It isn't.
So, suggested syntax is too ambiguous.
Regards,
--
Nicolas Goaziou
ny case, as it would affect every headline, not only the last
one in the buffer.
Regards,
--
Nicolas Goaziou
The risk of
false positive is too high. This is the reason why notes were never
considered as syntactically meaningful so far.
> The is taken from `org-log-note-headings'.
This is configurable, which is not a good idea for any new syntax.
Regards,
--
Nicolas Goaziou
Ihor Radchenko writes:
> I feel that my understand of "note" in context of org is different from
> yours. Is there a formal definition of "note" in org?
As I stated in my first post a few hours ago:
Notes are mostly free-form; there is no syntax describing them.
> However, we can formalise
Ihor Radchenko writes:
> I was mainly referring to org-add-note. The last note taken with
> org-add-note can be found quite reliably.
>
> I am using the following code saving the last note into :SUMMARY:
> property upon exiting the note buffer. Though it may be an overkill, not
> sure how easy
form; there is no syntax describing them. Org cannot tell
what is a "note". As a consequence, pointing to "the last note taken" is
not reliable, syntax wise.
Of course, under some assumptions (e.g., notes setup is fixed, you never
write notes by hand, ...), you could guess what the last note taken is.
But again, this is not reliable, and not portable.
Regards,
--
Nicolas Goaziou
d the string-match check breaks. Checking if title is non-nil fixes
> this.
Applied. Thank you.
Regards,
--
Nicolas Goaziou
Hello,
Naoya Yamashita writes:
> I found `ox-md` exporter drop src-block language information.
> My patch fixes the behavior.
This is a feature. "ox-md" exports to vanilla Markdown, which doesn't
support such syntax. You may want to use other back-ends, e.g.,
"ox-gfm&qu
he syntax
in LaTeX?
You may use radio tables to transform an Org table into a Markdown table
(whatever that means, vanilla Markdown doesn't support tables).
Regards,
--
Nicolas Goaziou
Vladimir Alexiev writes:
> Here's some code that works for me.
> It overwrites 2 org table functions, changing just one line (see "FIXED").
> Would be nice if this can be adopted in org; of course with a proper option
> etc.
You may suggest it to Markdown mode. I think this is a terrible idea
to make this conditional:
> (concat "+"
That will not work without changing Org syntax. Markdown and Org table
are incompatible.
Regards,
--
Nicolas Goaziou
Hello,
Samuel Wales writes:
> i presume the fix will come out in the next release of maint?
I applied the fix on master because it is built on top of another fix
from there. So no, it should be available in Org 9.4 only.
Regards,
--
Nicolas Goaziou
cannot see your LaTeX environment. You can use
\begin{equation*}
...
\end{equation*}
instead and lift the ambiguity.
Regards,
--
Nicolas Goaziou
ert large PDF
> into png images. Caused very long time suspend.
You can customize the variable and remove "pdf".
Regards,
--
Nicolas Goaziou
nd open (C-c C-e l o), observing
> missing items when the list below is exported:
> - [[file:loopy.org]]
> - [[file:loops.org]]
> - [[file:loopz.org]]
> - [[file:some-loops.org]]
> - [[file:some-loopz.org]]
Fun bug. This should be fixed (make sure to start from
foo.org::text]] text links,
and uses `occur' with [[foo.org::/text/]] links.
Wouldn't it be more idiomatic to use a regular text search here?
Regards,
--
Nicolas Goaziou
in `org-list-insert-item'. I pushed a fix and
a test for that.
Regards,
--
Nicolas Goaziou
property set to
"+TITLE: test" in the file "test.org"
Therefore, it is automatically removed in another context, e.g., in text
search.
However, the export process doesn't resolve text searches.
If you want to link to a specific part of the text, you can use
a target.
Regards,
--
Nicolas Goaziou
this
> :PROPERTIES:
> :ID: 129ed2c7-1ef2-4207-bb79-bfcec5fe6907
> :END:
> - [X] Done
> - [ ] Not done
>
> ,*** Other text
> And now the link, [[id:129ed2c7-1ef2-4207-bb79-bfcec5fe6907][[1/2] Link to
> this]].
> #+end_src
I cannot reproduce it. You may want to try master branch.
Regards,
--
Nicolas Goaziou
rks
^
???
You didn't say you were narrowing something.
Anyway, for the time being the error may come from Org Ref
(org-ref-delete-labels).
Regards,
--
Nicolas Goaziou
ersion of Org.
I updated the spec. Thank you.
Regards,
--
Nicolas Goaziou
.
> --8<---cut here---end--->8---
>
>
> This is the result. Note that the first paragraph, which is outside the
> selected region, is also filled.
Fixed. Thank you.
Regards,
--
Nicolas Goaziou
continue to work by setting the new variable
> eldoc-documentation-strategy, which puts eldoc in
> "backwards-compatability" mode.
Thank you.
Do we need another variable for that? Could
org-eldoc-documentation-funicton catch wrong-number-of-arguments error,
and try another call instead?
Regards,
--
Nicolas Goaziou
Hello,
Alexandru-Sergiu Marton writes:
> * lisp/ox.el (org-export-smart-quotes-alist): Add Romanian variants for
> smart quotes.
I added TINYCHANGE at the end of the commit message (assuming you
haven't signed FSF papers yet) and applied your patch.
Thank you!
Regards,
--
Nicolas Goaziou
ve comments about your
suggestion.
Regards,
--
Nicolas Goaziou
Jarmo Hurri writes:
> I think I am running the latest (stable) master:
Note: stable ≠ master, so you just wrote an oxymoron ;)
> Org mode version 9.3.7 (release_9.3.7-13-ge62ca4)
This is not quite HEAD. Mine is release_9.3.7-683-g95eaab.
d you try with latest master? I cannot reproduce it.
Regards,
--
Nicolas Goaziou
gt; table (instead of giving up with a user-error, I now get a nil).
Would you mind explaining?
> it works for me, and I don't see counterindications. is it
> worthwhile, offering you the patch?
Thank you. It may be so, but I may be missing some context.
Regards,
--
Nicolas Goaziou
to do so?
You can customize `org-structure-template-alist'. I don't remember if
that's possible in Org 9.1.9, tho.
Regards,
--
Nicolas Goaziou
ommand.
>
> 4. The second paragraph is not filled.
Fixed. Thank you.
Regards,
--
Nicolas Goaziou
Colin Baxter writes:
> Well, yes. But should it really be in an "example" source block?
Are you asking if this comma character is needed? This particular comma
is due to Org being over-cautious, and may be ignored. But you should
simply ignore it.
> If this is then exported and the author
e_9.3.7-669-g3327fb)
This is an escape character. See (info "(org) Literal Examples").
Regards,
--
Nicolas Goaziou
n ECM demonstrating the issue?
Regards,
--
Nicolas Goaziou
; No indentation:
> If the indentation is removed from the second line:
> 1. a
> b
> 2. c
>
> Then it might be working as expected:
> 1. a
> 2.
> b
> 2. c
>
> a correctly numbered list item is inserted.
>
> The fourth lines list number: 2. c
> didn't change, but it might be expected since there was no indentation
> before the: b
> therefore it might be assumed that the list ended there.
This is expected. You need to fix the second list manually, with C-c C-c.
Regards,
--
Nicolas Goaziou
Hello,
Albert Krewinkel writes:
> Eth and thorn are letters in the Icelandic alphabet, and the language
> is in active use.
>
> TINYCHANGE
Applied. Thank you.
Regards,
--
Nicolas Goaziou
rg-id-extra-values' to be a
> symbol that references another variable was removed. This change
> restores that functionality.
Thanks. I applied the patch. I also fixed the commit hash in the
message.
Regards,
--
Nicolas Goaziou
*") 'org-emphasis-bold)
(org-defkey org-mode-map (kbd "M-o M-*") 'org-emphasis-bold)
(org-defkey org-mode-map (kbd "M-o ~") 'org-emphasis-code)
(org-defkey org-mode-map (kbd "M-o M-~") 'org-emphasis-code)
(org-defkey org-mode-map (kbd "M-o /") 'org-emphasis
preciate some enlightenment on the topic. For example, could you show
what code your extension generates with the table above?
Regards,
--
Nicolas Goaziou
overlays, you can't have your cake
and eat it too.
> I am currently working on a patch to rewrite the whole folding system.
> Your issue should disappear once it is applied.
Yes, hopefully, switching to text properties will get us out of this sad
situation.
Regards,
--
Nicolas Goaziou
like PLOT[0] and PLOT[1], you
are effectively suggesting to write code, with conditionals.
Anyhow, I think it is more future-proof to use, and possibly improve
"ob-gnuplot.el" so it is easier to use, than to develop PLOT keywords.
WDYT?
Regards,
--
Nicolas Goaziou
f,a sdfasd fsdnjkfanksda d.ssa
> dkfasn df.
>
> what i get is a somewhat surprising creation of a new
> entry below the entry that contains the list. this occurs
> even with m-x org-insert-item, which imo should not affect
> entries at all.
I cannot reproduce it.
Regards,
--
Nicolas Goaziou
Sébastien Miquel writes:
> I meant to go from
>
> - Cogito,
> - ergo
> sum
>
> to
>
> - Cogito,
> - ergo
> sum
Structurally, this is weird. You are splitting a paragraph in two parts,
and sending the latter one into another item.
I think you can use regular Emacs commands,
Mario Frasca writes:
> again, my idea is that we're describing something new, and I'm
> wondering what lisp construct could be used to describe a table like
> this one:
>
> | h1 | h2 | h3 |
> |++|
> | 11 | 12 | 13 |
> | 21 | 22 | 23 |
> | 31 | 32 | 33 |
> |++|
> | a1 | a2
I have a header, a body,
> and a summary, and I'm only interested in the header and body, not the
> summary.
>
> just scattered thoughts … who fills in?
There is no such thing as a "table summary" in Org syntax.
Regards,
--
Nicolas Goaziou
of nested list, a way to cycle the indentation to that of
> the main or inside list would also be nice.
I'm not sure what you mean here.
Regards,
--
Nicolas Goaziou
Hello,
Mario Frasca writes:
> On 24/06/2020 02:19, Nicolas Goaziou wrote:
>>
>>>> This could be extracted as an independent function, which would return
>>>> the header, or nil. We can also imagine a function returning a cons cell
>>>> (HEADER . B
Hello,
Gustavo Barros writes:
> So, I'd like to kindly suggest that either "attachment" be included as
> a case in `org-lint-link-to-local-file' or that an equivalent check
> for attachments be included in `org-lint'. I'd be much thankful.
This is done in master.
Regards,
--
Nicolas Goaziou
a good idea, really. For this kind of complexity,
I suggest to consider using gnuplot source code blocks, with the table
as input.
Regards,
--
Nicolas Goaziou
these changes.
Thank you.
Regards,
--
Nicolas Goaziou
kers or extending
existing ones.
Allow me to polish up my draft a bit, so we can compare the benefits of
each system.
Regards,
--
Nicolas Goaziou
me draft lying
somewhere in that direction.
WDYT?
Regards,
--
Nicolas Goaziou
\end{description}
Regards,
--
Nicolas Goaziou
tches like this one from time to time.
Patches welcome, of course. However, the fontification will never be
perfect unless its internals are rewritten.
Regards,
--
Nicolas Goaziou
See https://www.markdownguide.org/basic-syntax#html-best-practices
Fixed. Thank you.
Regards,
--
Nicolas Goaziou
w functions into the
main system.
Regards,
--
Nicolas Goaziou
u need to (require 'ol-info)
Regards,
--
Nicolas Goaziou
g and
> test-writing.
I didn't know you hadn't signed FSF papers. Since we are in feature
freeze, and this is not a bug-fix, what about waiting until bureaucracy
is over?
Of course, this assumes you're planning to sign FSF papers.
Regards,
--
Nicolas Goaziou
Hello,
Mario Frasca writes:
> how do I run tests from the command line (I'm using make test) but
> then limited to one lisp file? or one specific test?
Use BTEST_RE="regexp" prefix, e.g.,
BTEST_RE="table" make test
Regards,
--
Nicolas Goaziou
stardiviner writes:
> I tested with command "emacs -q" and an minimal Emacs config. Both failed to
> started. I also record an screen video to show this problem.
>
> Link: https://pan.baidu.com/s/1iBbcStvNCwdN1vB8ivISdw password code:
> r6ws
I cannot see the video. But this isn't an ECM
(plist-put params :textind t)
>;; Write script.
>(with-temp-buffer
OK. Note you can go even further: nested `if' should be replaced with
a `cond'.
Also, further nit: (not (cl-every ...)) will apply `not' only once.
In any case, it would be better if refactoring happens while introducing
unit tests *hint*.
Regards,
--
Nicolas Goaziou
Hello,
writes:
> Isn't `seq-some' equivalent? (in this case, at least; cl-some is
> willing to take more than one sequence).
This is only tangential to your question, but, unfortunately, we cannot
use `seq-some' as Org still supports Emacs 24.3.
Regards,
--
Nicolas Goaziou
Hello,
Mario Frasca writes:
> On 13/06/2020 17:18, Nicolas Goaziou wrote:
>> Unit tests are not worth a formal definition. However, "test-ox.el"
>> contains unit tests.
>
> I'm not sure what you mean by the first sentence
I mean that, even though unit tests a
upport for LaTeX macros, i.e., this is not AucTeX. In
particular, it supports macros with at most one argument. With a proper
"latex_header" keyword, it should be possible to preview \ce{...}, but
not \SI{ … }{ … }. Likewise, the former will be correctly exported, but
not the latter.
Regar
framework. Try to export, e.g.,
| a |
| b |
|---|
| c |
in HTML. They are also assumed to be valid in the manual, per above.
So, if your question is: "should Org support multiple lines headers?",
I'd say that it already does, but it should definitely be made more
consistent across the various libraries (e.g., Org Plot).
Regards,
--
Nicolas Goaziou
to consider (4). I think (3) is
> only relevant if we go for (2), which I don't really like.
>
> What do you think?
Isn't COOKIE_DATA property there to disambiguate this situation?
Regards,
--
Nicolas Goaziou
is org-toggle-inline-images : this does
> not disable inline image preview (though it does *enable* it).
I cannot reproduce it. Calling `org-toggle-inline-images' twice bring me
back to link text. Could you try again with a minimal setup?
Regards,
--
Nicolas Goaziou
tion that `keyword'
> is normalized by being upcased
Applied. Thank you.
Regards,
--
Nicolas Goaziou
Since there was no negative feedback, I pushed to master.
Thanks.
e which - aside from the footer - contains only a
> single letter `n` as contents
I cannot reproduce it. You may want to test with a minimal set-up, and
possibly bisect your configuration.
Regards,
--
Nicolas Goaziou
de an ECM,
including your .mailcap?
Regards,
--
Nicolas Goaziou
g Code Blocks").
Improvements to the manual are welcome, of course.
Regards,
--
Nicolas Goaziou
the
> middle of editing the capture.
Applied. Thank you.
Regards,
--
Nicolas Goaziou
starting with a hline has no header. Therefore, I suggest to
avoid removing hlines at the beginning of a table, we would lose
information.
Regards,
--
Nicolas Goaziou
ght. I removed the warning for dir property. Thank you.
Regards,
--
Nicolas Goaziou
al header arguments in its multiple
forms, `org-export-use-babel'.
Adding one more could also add confusion.
Regards,
--
Nicolas Goaziou
w which
> code block it's
> asking to evaluate.
What is wrong with :eval no-export header? You can set it globally,
file-wise, tree wise, or per block.
Regards,
--
Nicolas Goaziou
feature freeze, but since the change was very small, and was
discussed a while before I applied it nonetheless.
I'm cc'ing Bastien for the heads-up, if he wants to revert this for 9.4
release.
Regards,
--
Nicolas Goaziou
Hello,
Leo Vivier writes:
> I’ve noticed that a comment on the caching of org-element wasn’t up to
> date, so I went ahead and updated it. I’ve also fixed a missing quote
> for one of the variables.
Applied. Thank you.
Regards,
--
Nicolas Goaziou
he regexp above, e.g.:
(concat (rx bol (zero-or-more (any " " "\t")) "#+end")
(if block-type
(concat "_"
(regexp-quote block-type)
(rx (zero-or-more (any " " "\t")) eol))
(rx (opt ":") (zero-or-more (any " " "\t")) eol)))
assuming `block-type' is the type of the block, or nil, i.e.,
(match-string 1) in the previous regexp.
> - (pcase (get-char-property-and-overlay (point) 'invisible)
> + (pcase (get-char-property (point) 'invisible)
> ;; Do not fold already folded drawers.
> - (`(outline . ,o) (goto-char (overlay-end o)))
> + ('outline
'outline --> `outline
> (end-of-line))
>(while (and (< arg 0) (re-search-backward regexp nil :move))
> (unless (bobp)
> - (while (pcase (get-char-property-and-overlay (point) 'invisible)
> - (`(outline . ,o)
> - (goto-char (overlay-start o))
> - (re-search-backward regexp nil :move))
> - (_ nil
> + (pcase (get-char-property (point) 'invisible)
> + ('outline
> +(goto-char (car (org--find-text-property-region (point) 'invisible)))
> +(beginning-of-line))
> + (_ nil)))
Does this move to the beginning of the widest invisible part around
point? If that's not the case, we need a function in "org-fold.el"
doing just that. Or we need to nest `while' loops as it was the case
in the code you reverted.
-
Regards,
--
Nicolas Goaziou
html exports.
SETUPFILE only imports keywords.
> Is there a way that I can "import" that snippet without rewriting it in
> every file I need it?
See (info "(org) Library of Babel")
Regards,
--
Nicolas Goaziou
hopefully, fixed in master.
Regards,
--
Nicolas Goaziou
Leo Vivier writes:
> Yeah, I’ve reached the same conclusion, and I agree that we could
> mention the normalisation in a docstring. Do you want me to take care
> of it?
Sure! Thank you.
Leo Vivier writes:
> I understand, but I think the function is also used to modify
> file-parameters like `#+title`. If you run `org-element-parse-buffer`
> on a buffer with the following content:
>
> [START]
> #+title: Foo
>
eight.)
I don't either. I didn't notice there was a difference until recently.
Regards,
--
Nicolas Goaziou
ain consistency. This might cause
> problems with some hard-coded upper case letters in the codebase, but
> I haven’t run into any issue so far.
This is unrelated to capitalization usage in Org buffers. Upcasing is
used to tell the difference between, e.g., :value and :VALUE.
Regards,
--
Nicolas Goaziou
> point is: as far as I can see, org-plot currently only recognizes its
> `#+' lines if they are immediately before the table. being new to
> this world, I a not aware of other `#+:' lines other than TBLFM
> and PLOT.
#+name: #+header: #+caption: #+results: #+attr_latex: #+attr_html: …
They all
ffiliated keyword at the end of
the table is a good idea, and I'm sure that allowing it on both ends is
a bad one.
Regards,
--
Nicolas Goaziou
: Reference ‘table’ not found in this buffer
>
> If I remove the "COMMENT" state on the heading, then the table is
> found.
This sounds correct. A commented section is dead code, after all.
Regards,
--
Nicolas Goaziou
501 - 600 of 10107 matches
Mail list logo
