mime-info mime-type))
>
> In 26.1, the value assigned is `view-mode'. In 27.0.50, the value assigned
> is "less '%s'".
I still cannot reproduce it, so your .mailcap file is different than
mine. Anyway, you can tweak `org-file-apps' variable to use whatever you
want to open the file.
HTH,
--
Nicolas Goaziou
show the link you're using? FWIW, I don't have trouble opening
links to directories.
Regards,
--
Nicolas Goaziou
t alignment expects a fixed-width face.
Regards,
--
Nicolas Goaziou
Hello,
Steven Penny writes:
> On Sun, Dec 29, 2019 at 8:08 PM Nicolas Goaziou wrote:
>> You can use angular links, e.g.,
>>
>> <https://developer.mozilla.org/docs/Web/JavaScript/Reference/
>> Global_Objects/String/lastIndexOf>
>
> Can you link to
l your message is
about setting up capture in various ways.
Could you update Org (Org 9.3.1 has been released last week) and try
again? Also, could you provide an ECM demonstrating how to reproduce the
issue in a simple way, not necessarily how you tried to work around
it ? :)
Thank you.
Regards
table.el tables, as their name suggest, are opaque to
Org mode. In particular, it doesn't know how to parse them. It just
feeds table.el with them at export time.
Regards,
--
Nicolas Goaziou
Hello,
Marco Wahl writes:
> A natural fix is committed, I think. Would be great if you could test
> this fix.
Thank you for the fix.
Could you refactor it so belongs to org-compat.el? For example, we could
create image-map keymap there if Emacs < 26.
Regards,
--
Nicolas Goaziou
Happy New Year,
--
Nicolas Goaziou
I haven't checked.
Regards,
--
Nicolas Goaziou
it? It looks correct. Otherwise, "./sunday.org" should
work.
Regards,
--
Nicolas Goaziou
it.
Regards,
--
Nicolas Goaziou
e.g.,
<https://developer.mozilla.org/docs/Web/JavaScript/Reference/
Global_Objects/String/lastIndexOf++[lastIndexOf]>
You can also use link abbreviations. Please refer to the manual for that
one.
Regards,
--
Nicolas Goaziou
c emacs-lisp :results table
> '(hline (hi . bye) (here . there) hline)
> #+end_src
>
> #+RESULTS:
> : (hline (hi . bye) (here . there) hline)
[...]
> Just wondering why it would distinguish between a trad list and
> a dotted list.
It's probably because no one bot
pplied it. Thank you!
Regards,
--
Nicolas Goaziou
Hello,
Thomas Fitzsimmons writes:
> I have signed FSF papers for contributions to GNU Emacs.
I updated your status, then. Thank you for letting me know.
Regards,
--
Nicolas Goaziou
Jack Kamm writes:
> However, the change here is very small, I just wrote a small patch and
> it's 15 insertions (+), 4 deletions(-), including the entry in
> ORG-NEWS. My understanding is that such small changes don't require
> explicit copyright assignment.
>
> Is it OK for me to send the patch
Hello,
Jack Kamm writes:
> I agree, this sounds like the correct behavior to me.
OK. Would you want to implement it?
Regards,
--
Nicolas Goaziou
x27;. Have you
tried it? It works here.
Regards,
--
Nicolas Goaziou
. If you did, please let me
know.
Regards,
--
Nicolas Goaziou
- `split-window-below'
- `split-window-right'
- `reorganize-frame'
OTOH, values that use the current layout should not restore it
afterwards:
- `current-window'
- `other-window'
- `other-frame'
This should be mentioned in the docstring.
WDYT?
Regards,
--
Nicolas Goaziou
d your name to the list of contributors who haven't signed FSF
papers. Please let me know if you did so I can update your status.
Regards,
--
Nicolas Goaziou
the ORG-NEWS file accordingly. Please let me
know if there's something suspicious.
Sorry for the inconvenience.
Regards,
Footnotes:
[1] <https://lists.gnu.org/archive/html/emacs-orgmode/2019-12/msg00312.html>
--
Nicolas Goaziou
Nicolas Goaziou writes:
> IMO, it would be more productive to think about what can be done in your
> situation instead. For example, one solution could be to require "[[" to
> be escaped in a link (current syntax already requires closing brackets
> to be escaped in some si
mmit-messages I added
> the TINYCHANGE cookie. Tests (make test) are passing.
Applied. Thank you!
Regards,
--
Nicolas Goaziou
ak the inline image preview » is rather vague.
In any case, I'm Cc'ing Tom Gillespie as he may know what is happening.
> If possible, I think Org Mode should add test for inline image.
Patches welcome :)
Regards,
--
Nicolas Goaziou
be escaped in some situations). I'm not yet sure how to deal with it,
tho.
Regards,
--
Nicolas Goaziou
I can record it in our contributors file.
Regards,
--
Nicolas Goaziou
nce you write
[[This is a paragraph with [[https://google.com][a link]]
^^
the underlined part becomes the link.
I agree this is not optimal. Yet, I'm not sure about how to deal with
this.
Regards,
--
Nicolas Goaziou
;
> to guix-patches (here in CC, I'm also forwarding my original patch
> submission here), but I've been suggested to send the patch upstream.
>
> What do you think? I can submit a proper patch if needed (but feel free
> to patch it yourself)
It sounds good. Could you send a patch against "maint" branch?
Thank you.
Regards,
--
Nicolas Goaziou
7;@1'. I have a few qualms about this table section in general, but felt
> that this particular typo was an important one to highlight.
You are right. Fixed.
The manual definitely needs to be improved in that area (remote
references).
Thank you.
Regards,
--
Nicolas Goaziou
y 819e98afd018cad3c13fd58bfcbd979ab36dfbc7 was necessary. I'm
Cc'ing Matt Price.
Regards,
--
Nicolas Goaziou
lls and lists." without being
> specific, I assume this behavior is a bug.
It isn't. Table.el tables are opaque to Org. IOW, Org doesn't handle
table.el tables at all.
In the manual, unless it is specified otherwise, "table" refers to Org
tables, not table.el tables.
Regards,
--
Nicolas Goaziou
gest to unravel what is needed at runtime and what is required
at export time.
Regards,
--
Nicolas Goaziou
)) '(target radio-target))
or
(org-element-lineage (org-element-context) '(target radio-target) t)
Regards,
--
Nicolas Goaziou
mit message since I don't know
if you have signed the FSF papers. If you did, please let me know.
Regards,
--
Nicolas Goaziou
des
very simple constructs. If you want to insert elaborate LaTeX code, you
can always use:
#+begin_export latex
...
#+end_export
Regards,
--
Nicolas Goaziou
Hello,
Kyle Meyer writes:
> Nicolas Goaziou writes:
> Sorry, I don't have write access. But this issue seems to be about the
> Org ELPA tarball, so I don't understand how it'd be related to the
> recent Org sync with the Emacs repo.
That's because I misread
ppreciated.
FWIW, I simply suggest not bothering writing tests for fontification.
Regards,
--
Nicolas Goaziou
tring -1 nil) "\n")
Minor nitpick:
(if (string-suffix-p string "\n") ...)
is slightly less low-level.
Thank you.
Regards,
--
Nicolas Goaziou
is to functionp allows a lambda to be specified and is
> consistent with what org-capture-set-target-location allows.
Fixed. Thank you for the report and the analysis.
Regards,
--
Nicolas Goaziou
ual, if appropriate, and add a few tests in
`test-org/auto-repeat-maybe' located in test-org.el file?
Thank you!
Regards,
--
Nicolas Goaziou
xinfo file for the
Org guide. It may be an issue related to how Org was merged with Emacs.
I'm Cc'ing Kyle, as I think he has write access to Emacs repository, and
can fix it.
Thank you.
Regards,
--
Nicolas Goaziou
...
(add-text-properties
beg-of-endline
(min (point-max) (if whole-blockline beg-of-next-line end-of-endline
I'm also not convinced that the (min (point-max) ...) left is necessary.
Could you send an updated patch (on top of maint)?
Regards,
--
Nicolas Goaziou
.3 and Emacs 26.3, I cannot
reproduce your problem.
Regards,
--
Nicolas Goaziou
may want to update Org. Mine is 9.3.
Regards,
--
Nicolas Goaziou
x
> environment should be numbered.
I applied your patch on maint, since it is arguably a bugfix, so
I dropped the ORG-NEWS entry. Sorry for the extra work.
Thank you.
Regards,
--
Nicolas Goaziou
Hello,
Jason Dunsmore writes:
> I've addressed each of your points in my updated patch (attached).
Applied. Thank you.
I added you to the list of contributors who have not signed FSF papers.
Let me know if you did.
Regards,
--
Nicolas Goaziou
erating directly on the element will be a bit nicer. Why do you need
`org-remove-indentation'?
Could you send an updated patch and provide an ORG-NEWS entry (on top of
master)?
Regards,
--
Nicolas Goaziou
xpand within source blocks. It tried to expand macro in
your table header, but cannot find the macro definitions.
>
> Both File A and File B had identical LaTeX settings, i.e. the macro was
> defined in both files.
Where is it defined? I cannot see it.
Regards,
--
Nicolas Goaziou
bout how this limitation, if it exists,
> should be expressed in documentation. Shall I give it a try?
Sure, but please do not mix SETUPFILE and INCLUDE, which are unrelated.
Regards,
--
Nicolas Goaziou
change. I think
I got it already.
> It should have been added as an option, so either static or dynamic
> behaviour can be selected by the user.
I didn't think so two years ago, when I implemented this, and I still
don't think so.
Regards,
--
Nicolas Goaziou
locks?
I do not understand. Source and example blocks are verbatim blocks,
whereas verse blocks are not. There is nothing to match, is there?
Regards,
--
Nicolas Goaziou
ented behaviour does not match the
current state.
Regards,
--
Nicolas Goaziou
the time interval above is correct? I would also
expect an error from that time specification.
Regards,
--
Nicolas Goaziou
-function org-dynamic-block-define)
> (org-dynamic-block-define "clocktable" (quote org-clock-report))
This looks like a FrankenOrg. Your installation is suspicious. I don't
know what is "paradox", but you may want to check if all loaded
libraries are correct (e.g., b
ote which basically removes the `progn` block and
>replaces it by a single `setq`.
Fixed. Thank you for the report and the patch.
Regards,
--
Nicolas Goaziou
recursively loads configuration from other files,
without inserting anything. INCLUDE keyword recursively inserts contents
from other files in the current document, but there is no guarantee that
configuration from these files will be inherited.
As a rule of thumb, if you want to access to metadata (i.e., keywords),
use SETUPFILE, if you are interested in contents, use INCLUDE. Note that
you can have both for a single file.
Regards,
--
Nicolas Goaziou
ines inside all block types. Example and source blocks highlight
> as if the text is escaped, diverging from the behavior of org-mode.
> Verse blocks highlight as a headline, in agreement with the behavior.
This is the expected behaviour. See (info "(org) Literal Examples")
Regards,
--
Nicolas Goaziou
Kiwon Um writes:
> I didn't know what the issue in the past interpretation was, but I am
> just not sure whether it's a good idea to enforce that we must use
> such a special character, which we cannot directly see from the
> editor.
This is because you are using an ambiguous construct. There ar
Hello,
Jarmo Hurri writes:
> I find current behaviour inconvenient, because I want to set common
> global properties for a large number of files, and I can not currently
> do this via an included file.
What happens if you use SETUPFILE instead?
Regards,
--
Nicolas Goaziou
How do I get the old behaviour back, rather than the new breakage ?
I will try to ignore the sarcasm, or whatever you may call it, from your
answer.
AFAICT, you still can have cells wider than their contents, e.g., try
`C-c TAB` on the table below.
| <30> |
| foo |
Regards,
--
Nicolas Goaziou
u want to include the
brackets, you need to escape them, as explained in the ORG-NEWS
document, or in the manual:
[[https://somewhere-to-url][\[My Link\]]]
Regards,
--
Nicolas Goaziou
ey use its value to start lists at an
appropriate number, if technically possible. I suggest org-re-reveal to
do the same if that's not the case.
Regards,
--
Nicolas Goaziou
Tomasz Piotrowski writes:
> Many thanks for the reply. Please find the backtrace attached. This
> variable org-enable-table-editor has been removed in org v.9.1., which
> is stated explicitly in the release notes for v.9.1:
> https://orgmode.org/Changes_old.html
>
> I use v.9.2.6. The error appea
et :tree-type)
(`week ...)
...)
> + (if (eq time-grouping 'day)
> + (org-datetree--find-create
> +"^\\*+[ \t]+%d-%02d-\\([0123][0-9]\\) \\w+$"
> + year month day)
Please use `when' (or `unless') instead of one-armed `if'.
Could you send an updated patch?
Regards,
--
Nicolas Goaziou
ntain any reference to this variable. This may be related to
your configuration.
Regards,
--
Nicolas Goaziou
Hello,
Sebastian Miele writes:
> Sorry. I messed up the previous mail. Please ignore it.
Applied. Thank you.
Regards,
--
Nicolas Goaziou
tring= (file-name-extension out-file) "xmi")
> '("-txmi"))
> + ((string= (file-name-extension out-file) "scxml")
> '("-tscxml"))
> + ((string= (file-name-extension out-file) "html")
> '("-thtml"))
> + ((string= (file-name-extension out-file) "txt")
> '("-ttxt"))
> + ((string= (file-name-extension out-file) "utxt")
> '("-utxt")))
Could you use
(pcase (file-name-extension out-file)
("png" ...)
...)
instead?
Regards,
--
Nicolas Goaziou
lifies as a bugfix or as a new feature? In the latter case, could you
rebase it on top of "next" branch and add an entry in ORG-NEWS, under
"Org 9.4" section?
Thank you!
Regards,
--
Nicolas Goaziou
Hello,
Michael Wu writes:
> No, I cannot. Perhaps my version is out of date.
OK. Then I'm closing this bug report. Feel free to re-open it if you
find anything wrong.
Thank you for replying.
Regards,
--
Nicolas Goaziou
Hello,
Michael Wu writes:
> C-c C-x C-l is what removes the preview images, not C-c C-c as suggested in
> the info note.
I cannot find the paragraph you're talking about. Can you see it in the
manual at <https://orgmode.org/org.html>?
Thank you.
Regards,
--
Nicolas Goaziou
rt of the ‘\title’-macro". These descriptions seem
> to say the exact opposite of each other.
I fixed the documentation in the yet-to-be-released Org.
Thank you.
Regards,
--
Nicolas Goaziou
Hello,
Sebastian Miele writes:
> That's perfectly fine with me. An updated patch is attached.
Applied. I removed the ORG-NEWS entry because it is more a bugfix than
anything else.
Thank you.
Regards,
--
Nicolas Goaziou
g-src--contents-for-write-back'.
WDYT?
Regards,
--
Nicolas Goaziou
)
>
> then, open a (presumably empty) file, foo.org, say, and type
>
> | this | is | a | test |
>
> then, at the end of the line, hit , and type, e.g., "t" (or
> ) and the error appears.
FWIW, I cannot reproduce it.
Regards,
--
Nicolas Goaziou
ource buffer instead of that from the editing buffer.
Thank you.
Would you mind explaining your use case?
Regards,
--
Nicolas Goaziou
Hello,
Arne Babenhauserheide writes:
> The javascript license notice by org-mode is not recognized by
> librejs.
Would you want to provide a patch for that?
Thank you.
Regards,
--
Nicolas Goaziou
.0, NS
> appkit-1671.20 Version 10.14.3 (Build 18D109))
> of 2019-09-02
> Package: Org mode version N/A (N/A !!check installation!! @
You may want to check your Org installation, according to the advice
above.
Regards,
--
Nicolas Goaziou
Thibault Polge writes:
> As you can see, the LaTeX PDFs have everything in a single line, the
> HTML output displays four separate paragraphs.
This is because the definition of a paragraph in HTML, or LaTeX,isn't
the same as in Org. In this particular case, HTML matches Org
definition. LaTeX is
t;
> Wide Web
>
> !
>
>
> I wouldn't except these lines to introduce any paragraphs break.
Of course they should. You should look at the definition of a paragraph,
per Org syntax. Keywords cannot belong to a paragraph.
Regards,
--
Nicolas Goaziou
(HTML #). Other attested names in Unicode are:
> pound sign, hash, crosshatch, octothorpe.
> - U+FF03 ＃ FULLWIDTH NUMBER SIGN (HTML ＃)
> - U+FE5F ﹟ SMALL NUMBER SIGN (HTML ﹟)
This is left as an exercise to the reader. ;)
Regards,
--
Nicolas Goaziou
Hello,
Thibault Polge writes:
> According to Org-Mode documentation[1],
See <https://orgmode.org/worg/dev/org-syntax.html#Comments> (with a nice
typo...)
Regards,
--
Nicolas Goaziou
try to use keywords, e.g.,
#+attr_latex: :title Whatever
Foo...
Changing the syntax is the very last thing to consider, IMO.
Regards,
--
Nicolas Goaziou
Hello,
Ken Mankoff writes:
> On 2019-10-16 at 12:38 +02, Nicolas Goaziou wrote...
>
> Would you accept a documentation patch that defines the current
> behavior?
I don't know enough of the problem to answer. A default answer which in
neither "yes" or "no"
Hello,
Jens Lechtenboerger writes:
> Thanks! A patch is attached.
Applied. Thank you.
Regards,
--
Nicolas Goaziou
those examples I can't get deeper called functions to
> know if the nth-parent was called interactively or not.
IMO, this is what you shouldn't try to do: mess with the call stack.
This sounds like a wrong approach to the problem.
Regards,
--
Nicolas Goaziou
call to a function is
interactive, or not.
So, if you want to implement it properly, you may want to look into that
direction.
Of course, meawhile, do not rely on undefined behaviour :)
Regards,
--
Nicolas Goaziou
Hello,
wlharvey4 via Emacs-orgmode writes:
> Is it possible to inject the value of a macro into code using
> a variable?
No, macros are mostly text replacement. They are not Babel related.
You may want to pass arguments to Babel blocks using other Babel blocks.
Regards,
--
Nicolas Goaziou
gt;
> <>
> <>
> <>
> <>
> #+end_src
>
> C-c C-v C-v is already very slow, takes ~15 seconds to resolve the references
> (can be seen in the Emacs Profiler), even though the inclusion graph is
> very simple.
Please try a more recent version of Org. Release 9.1.9 is pretty old. It
might be fixed already.
Regards,
--
Nicolas Goaziou
ad-list, from org-babel-ocaml-parse-output, from
> org-babel-execute:ocaml, the code being modified.
Since no-one commented your patch, I applied it. I added TINYCHANGE
cookie at the end of the commit message, since I don't know if you
signed the FSF papers already.
Thank you for your contribution!
Regards,
--
Nicolas Goaziou
Hello,
Robert Irelan writes:
> Patch attached
Thank you.
However, I couldn't apply your patch since manual changed quite a bit in
this area not so long ago. I adapted your patch to the new structure and
applied it.
Regards,
--
Nicolas Goaziou
urce code lines should
> be wrapped in code elements or not.
> * doc/org-manual.org: Document the new option
Applied. Would you mind adding an ORG-NEWS entry about it?
Thank you.
Regards,
--
Nicolas Goaziou
)
IIRC, the label has to be included in the caption command. I applied
a different solution. Let me know if that works for you.
Regards,
--
Nicolas Goaziou
UC, what you are suggesting. Once everything is
in place, your ideas could be integrated as an alternate priority system
within Org.
In any case, I cannot help much you with this, as the time I can devote
to Org is virtually non-existent these days. Hopefully, someone else can
guide you, if necessary. Do not worry much about breaking code: do write
tests!
Regards,
--
Nicolas Goaziou
thoughts?
I agree with the nil default value.
> +(defcustom org-html-wrap-src-lines t
> + "If t, wrap individual lines of source blocks in \"code\" elements.
When non-nil, wrap...
Regards,
--
Nicolas Goaziou
Hello,
Anton Latukha writes:
> Another two small patches.
Please merge the two patches and factor out the (- org-lowest-priority
...) while you're at it.
Thank you.
Regards,
--
Nicolas Goaziou
Hello,
Anton Latukha writes:
> * org.el (org-get-priority): Fix to allow the use of custom priority
> getters.
> Provide the headline as argument to the custom priority getter
> function.
Applied. Thank you.
Regards,
--
Nicolas Goaziou
Hello,
Robert Irelan writes:
> Patch to fix attached
Applied. Thank you.
Regards,
--
Nicolas Goaziou
fusing.
It could mean, e.g., a string.
Regards,
--
Nicolas Goaziou
Hello,
Mario Schlegel writes:
> * lisp/ox-latex.el (org-latex-src-block): Extend :placement attribute
> to source blocks when the minted package is used.
Applied. Thank you!
Regards,
--
Nicolas Goaziou
901 - 1000 of 9824 matches
Mail list logo
