Matt Huszagh writes:
> Hello,
>
> This patch omits a file description when :file-desc has a nil
> value. Previously, the following src block
>
> #+BEGIN_SRC asymptote :results value file :file circle.pdf :file-desc
> :output-dir img/
> size(2cm);
> draw(unitcircle);
> #+END_SRC
>
> would
On Thursday, 3 Sep 2020 at 14:29, Bastien wrote:
> IMHO it deserves a small addition to etc/ORG-NEWS.
Already there although maybe I added it in the wrong section? I put it
under Version 9.4 -> New options.
--
: Eric S Fraga via Emacs 28.0.50, Org release_9.3.7-725-g7bc18e
Bastien writes:
> Hi again,
>
> Eric S Fraga writes:
>
>> Patch attached. Comments welcome, of course.
>
> IMHO it deserves a small addition to etc/ORG-NEWS.
>
> Can one of you add it?
v2 (87imd33mys@ucl.ac.uk) included a NEWS entry.
I get one file, "foo.el", with both src blocks.
Chuck
> On Sep 3, 2020, at 1:31 PM, Enze Chi wrote:
>
> Hi Charles:
>
> Thanks for the clear explanation. Add default ":tangle yes" does what I
> expected.
>
> But when I try to tangle it to a file like this (with default ":tangle no"):
>
Hi Charles:
Thanks for the clear explanation. Add default ":tangle yes" does what I
expected.
But when I try to tangle it to a file like this (with default ":tangle no"):
(org-babel-tangle nil "foo.el")
I end up get 2 files:
foo.el:
(setq foo "hello")
test_tangle.el:
(setq bar "world")
Should
Ihor Radchenko writes:
> > I didn't know that eval specs support multi-line sexps, but seems that
> > works, so I can indeed use this. Thanks for the suggestion.
>
> Hmm. According to manual, it should support multi-line string. Not sure
> about sexps.
AFAIR it didn't work in the past. I
> I didn't know that eval specs support multi-line sexps, but seems that
> works, so I can indeed use this. Thanks for the suggestion.
Hmm. According to manual, it should support multi-line string. Not sure
about sexps.
In the worst case when you absolutely want multi-line sexp to be really
Not a bug. See inline.
> On Sep 3, 2020, at 12:37 AM, Enze Chi wrote:
>
>
> Remember to cover the basics, that is, what you expected to happen and
> what in fact did happen. You don't know how to make a good report? See
>
> https://orgmode.org/manual/Feedback.html#Feedback
>
> Your
Ihor Radchenko writes:
> I do not think there is support of multi-line planning everywhere.
I see.
> You can always use file-local definition at the beginning or end of your
> org file. Below is an example of local definition at the end of an org
> file.
>
> # Local Variables:
> # eval: (defun
Nicolas Goaziou writes:
> Hello,
>
> Eric Abrahamsen writes:
>
>> I've been trying to find a way to cordon off the bottom of my Org files,
>> to create an area for file-local variables and "LocalWords" and what
>> have you that Org doesn't consider part of the file's final heading.
>>
>> The
> org-insert-link (C-c C-l) will read a file name from you if you select
> "file:" or call it with a prefix argument.
This will do, thanks!
ср, 2 сент. 2020 г. в 03:08, Kyle Meyer :
>
> Dmitrii Korobeinikov writes:
>
> > Hi, all!
> >
> > Is there a way to provide completions for paths
> >
> Multi-line sexps in time stamps work would just be nice to have. Would
> it be hard to achieve? I mean, since multi-line %%(...) entries already
> work...
The problem is that org-mode assumes that planning line must be a single
line and a lot of internal logic hard-code this assumption.
For
> It can? Thatʼs not documented, as far as I can tell.
It is literally called "diary sexp". You can use any elisp sexp there,
like (let ...) or (or ...) or (function-name ...)
Robert Pluim writes:
>> On Thu, 03 Sep 2020 21:35:54 +0800, Ihor Radchenko
>> said:
>
> >> When dealing
Hello Bastien,
My current work-around is to map F12 to (org-mode-restart).
After installing a fresh version of Emacs 27.1 using the Windows
installer, and copying
org-9.3.7 to ~/.emacs.d, the first file I open is not colorized until
I use F12. My init.el contains:
(add-to-list 'load-path
Hello Bastien,
Below I've included some quick (hopefully useful) notes on the
changes
I've made.
Bastien writes:
p.s. If you'd like a TLDR on that website thread I started I'd
happily
attempt one. I just hope you don't find me too presumptions
going as far
as I have without having
> On Thu, 03 Sep 2020 16:46:48 +0200, Michael Heerdegen
> said:
Michael> Robert Pluim writes:
>> It can? Thatʼs not documented, as far as I can tell.
Michael> As a user, I read "Diary-style expression entries" in the org
manual as
Michael> including my own defined
Hi Timothy,
TEC writes:
> Ah, I see. I was going off a line in
> https://orgmode.org/worg/org-contribute.html
> "If you are undertaking big changes, please create a dedicated branch"
>
> I'm not sure if ~10 commits counted, but thought this may be the way to
> go. Once again, thanks for
Robert Pluim writes:
> It can? Thatʼs not documented, as far as I can tell.
As a user, I read "Diary-style expression entries" in the org manual as
including my own defined diary sexps - excluding them would be a
surprise that should be documented (no, I don't want that to happen!).
Michael.
> On Thu, 03 Sep 2020 21:35:54 +0800, Ihor Radchenko
> said:
>> When dealing with complicated date rules it can likely happen that a
>> diary sexp doesn't fit into one line.
Ihor> Diary sexp can be a user-defined function. If your sexp needs to span
Ihor> multiple
Ihor Radchenko writes:
> > When dealing with complicated date rules it can likely happen that a
> > diary sexp doesn't fit into one line.
>
> Diary sexp can be a user-defined function. If your sexp needs to span
> multiple lines, it is probably worth defining a function and simply
> using
> When dealing with complicated date rules it can likely happen that a
> diary sexp doesn't fit into one line.
Diary sexp can be a user-defined function. If your sexp needs to span
multiple lines, it is probably worth defining a function and simply
using <%%(your-function)> as a timestamp.
Best,
> I don't have a strong opinion here.
>
> Why do you think it would it be a better as a default?
It seems that other people expect it to be default [1]. Also, I am using
org-attach heavily in my workflows. Most of the time I found myself
inserting the link to attachment right after attaching a
That is understandable; they're big patches. I recommend going over ob-java
first. Java is probably more familiar to you and ob-java and ob-haxe are
very similar. These were mostly based on ob-python and ob-C. The tests are
based on ob-Cs tests.
Look carefully at org-babel-temp-dir and
Robert Pluim writes:
> I can push my change to org, but Iʼm not a regular org contributor, so
> Iʼd prefer to hear from one of the maintainers first.
Sorry - I meant, I see no reason to touch the existing code. No need to
change anything for what I want.
> Michael> This doesn't work:
>
>
Hi Christopher,
Kyle Meyer writes:
> Christopher W. Ryan writes:
>
>> how do I create next, previous, and up navigation links when exporting
>> to html, like in the org mode manual:
>>
>> https://orgmode.org/manual/HTML-specific-export-settings.html
>
> I think that's created in a two-step
Hi again,
Eric S Fraga writes:
> Patch attached. Comments welcome, of course.
IMHO it deserves a small addition to etc/ORG-NEWS.
Can one of you add it?
--
Bastien
Hi Bastien!
Great to see you back on the lists again :)
Bastien writes:
> Good guess :) I'm rolling up my sleeves to get to 9.4 ASAP so that
> we can commit features in the master branch again soonish.
>
> Still, you can share patches on the list, that's useful to discuss
> and improve
Hi Ihor,
Ihor Radchenko writes:
> The default value of org-attach-store-link-p is nil for now.
> Would it make more sense to set it to something else (say, 'attach)?
> I believe that 'attach or t would be better as a default.
>
> Thoughts?
I don't have a strong opinion here.
Why do you think
Hi Timothy,
TEC writes:
> Are we still in a feature freeze?
Yes.
> At the start of June Bastien announced a feature freeze (Release
> 9.3.7). As we are now moving into September, I'm wondering if this
> is still in effect? I can't see any recent emails from Bastien
> either so I'm guessing
Kyle Meyer writes:
> Kyle Meyer writes:
>
>> I'll let this sit for another day to see if other comments come in.
>
> Applied (e8ebf5d6c).
A welcome enhancement - thanks Eric and Kyle!
--
Bastien
Hi Dominick,
Dominick Samperi writes:
> No colors appear in first file opened. Must use (org-mode-restart)
> to enable colors after opening first file.
Can you provide a reproducible recipe?
--
Bastien
Hi Diego,
Diego Zamboni writes:
> Just a quick update: issue
> https://github.com/purcell/package-lint/issues/89 submitted by Kaushal
> has been closed through the PR I submitted, so now package-lint
> officially accepts "org-" symbols in "ox-" and "ob-" packages :)
Thanks for taking care of
Hi Richard,
Richard Lawrence writes:
> I haven't tested it extensively, and the code can surely be improved,
> but it works for the cases I could think to test.
thanks for writing and sharing this - perhaps you can add a link to
this message in https://orgmode.org/worg/org-hacks.html ?
Best,
stardiviner writes:
> This is really great to get official support for Org Mode.
+1! Thanks Ivan.
--
Bastien
Hello,
Ihor Radchenko writes:
> I may miss something, but it does not look [for me] any more specific
> in comparison with headline format:
>
> - headline :: "^\*+ .+$"
> - first line of note :: "^[ \t]*-.+$"
I do see a big difference, tho. Starting a line with an asterisk
followed by a
When doing org captures using the datetree format, newly added headlines
do not follow the value of `org-blank-before-new-entry'. This seems to
be the fault of `org-datetree-insert-line' using `insert' as opposed to
`org-insert-heading' to do its work. See the attachment for a proposed
fix.
Hello,
Eric Abrahamsen writes:
> I've been trying to find a way to cordon off the bottom of my Org files,
> to create an area for file-local variables and "LocalWords" and what
> have you that Org doesn't consider part of the file's final heading.
>
> The usual Emacs thing to do seems to be
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
Does refreshing the buffer work too? If so, I’ve had the same issue for a
while, but never really knew what was going on?
Matt
>
> On Sep 2, 2020 at 10:20 PM, mailto:djsamp...@gmail.com)>
> wrote:
>
>
>
> No colors appear in first file opened.
Matt Huszagh writes:
> This patch omits a file description when :file-desc has a nil
> value.
I've modified the patch to yield the same effect when executing a source
block.
Matt
>From 24d156e421973b5a97f1c797d48f1daa95348898 Mon Sep 17 00:00:00 2001
From: Matt Huszagh
Date: Wed, 2 Sep 2020
Hello,
This patch omits a file description when :file-desc has a nil
value. Previously, the following src block
#+BEGIN_SRC asymptote :results value file :file circle.pdf :file-desc
:output-dir img/
size(2cm);
draw(unitcircle);
#+END_SRC
would yield
#+RESULTS:
41 matches
Mail list logo