So, my point is the following. A shebang is an almost universally
accepted way to specify which interpreter should be used for code
evaluation.
In the ob-core.el, at line 787, the function called
org-babel-expand-src-block makes a buffer out of the noweb-expanded
code.
(I am working with org 20200
Kyle Meyer writes:
> Can't you inspect the return value of org-git-version?
That can work out, though unless I'm missing something, I need to move
to the org-mode repository, ask "git branch --contains", and parse the
output. Possible, but somewhat involved.
(TIL: git-describe's "{tag}-{nbcomm
Hi Gustavo,
Gustavo Barros writes:
> As of recently, repeating tasks are no longer showing up in the agenda
> for future dates. Below a minimal example of the issue:
Just confirming this issue, to make sure we don't forget it.
--
Bastien
> Such behavior exists for ages, at least since 8.2.10 till current master.
I can reproduce this.
The reason of error is simple: help buffers for key combinations where
not considered when writing help: link type.
Current code does not even store the link to such help buffers correctly
- when the
Bastien writes:
> Kévin Le Gouguec writes:
>
>> Bastien writes:
>>
- During the development of 9.4, AFAICT, while the "Version:" comment in
org.el sayd "9.4-dev", the org-version variable matched the latest
tag, i.e. 9.3.x.
I therefore couldn't figure out a way to
Hello,
In an attempt at automating a part of my workflow, I found that
org-capture's %l didn't quite fit what I needed. Normally,
org-store-link does the right thing, but for some capture tasks, I want
to custom generate the description, so %l doesn't work. I've attached a
patch that adds %L, a
as some have mentioned keystrokes, i just wanted to point out htat the
idea here is select with mouse and run using mouse, with no keyboard
at all. firefox org-capture does this for me. in case there was any
confusion.
On 9/9/20, Russell Adams wrote:
> On Mon, Sep 07, 2020 at 10:05:38PM -0700,
Kyle Meyer writes:
> I also don't find the current behavior particularly intuitive. (I'm
> also not really a babel user, so my opinion probably shouldn't count for
> much.) If we were adding it today, I think what you describe would be
> better, but, as you mention, breakage also now also weigh
Bastien writes:
> Prefer
>
> * lisp/ob-latex.el (org-babel-latex-preamble): New option for LaTeX
> preamble customization.
>
> "New option" is quite standard, an "option" being a customizable
> variable. In this case, "New option" would probably be enough, given
> the name of the option is q
Hi Matt,
Looking good here. Thanks!
Tom
On Wed, Sep 9, 2020 at 12:06 PM Matt Huszagh wrote:
>
> Tom Gillespie writes:
>
> > [...] I have a number of use
> > cases that I can imagine would benefit greatly from being able to
> > define a :header-args: :header (lambda () "yay!") property as a
>
Bastien writes:
> Also, if we integrate the change, `eval-default-headers' would be
> better named `org-babel-eval-default-headers'.
I've changed the function name to `org-babel-eval-headers'. The reason
for dropping "default" is that this function is now used as part of
`org-babel-merge-params'
Tom Gillespie writes:
> [...] I have a number of use
> cases that I can imagine would benefit greatly from being able to
> define a :header-args: :header (lambda () "yay!") property as a
> closure (and actually I assumed that it would just work that way if I
> tried to do it, clearly not though).
Bastien writes:
No Wayman writes:
Well, back to square one -- the "fix" breaks setting the end
time
of an existing schedule timestamp for me with.
I reverted it as 771c66f79.
Unfortunate, but I see the same breakage with the patch. I stepped
through trying to set and end time of an exi
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.
FWIW, I'm not convinced there's a
Either I missed something obvious or org-store-link from a help page for
a keystroke works incorrectly
Let's try to save a link to the *keystroke* help for e.g. org-insert-link:
1. Open help page with =C-h k C-c C-l=
2. Switch to the help buffer =C-x o=
3. Store link =M-x org-store-link RET=
4.
On 9/5/20 4:03 AM, Bastien wrote:
... I applied your change on the master branch as 471054136, thanks for this.
And thank you Bastien!
--
Anthony Carrico
Hi Timothy,
TEC writes:
> From memory, Doom actually has a number of rather nice Org patches that
> it hoards :P IIRC simply to avoid the effort of going through the patch
> process, and have more flexibility (using Doom convenience macros, etc.).
>
> See
> https://github.com/hlissner/doom-macs
I have set org-odt-preferred-output-format to docx, which works fine.
How can I have the intermediate odt-file removed automatically after
the docx-file is created?
Many thanks in advance for any answer
Rainer
--
Prof. Dr. Rainer Thiel
Institut für Altertumswissenschaften
07737 Jena, Germany (EU
Hi Eric,
Eric S Fraga writes:
> Also support for org-indent-mode: having the text align nicely with the
> heading (as it does with monospace typefaces) would be more visually
> pleasing.
>
> But I have a feeling that the calculations required for this and the
> above may be significant and argua
akater writes:
> Bastien writes:
>
>> IIUC this is a refactoring, it does not add or remove functionalities?
>
> Yes, just a refactoring.
In any case, let's discuss this for after 9.4.
Thanks,
--
Bastien
Dear Klaus,
I am not aware of code that does that.
Carsten
On Wed, Sep 9, 2020 at 3:55 PM Klaus Thoben wrote:
> Carsten Dominik writes:
>
> > On Wed, Sep 9, 2020 at 3:06 PM Eric S Fraga wrote:
> >
> >> On Wednesday, 9 Sep 2020 at 14:35, Klaus Thoben wrote:
> >> > Does such a function exist
Bastien writes:
> IIUC this is a refactoring, it does not add or remove functionalities?
Yes, just a refactoring.
A typo crept into comments and help pages, so here's an update.
signature.asc
Description: PGP signature
>From 0636f032b3c7e60221c28aeea91cce58376561dd Mon Sep 17 00:00:00 2001
F
Hello,
Ihor Radchenko writes:
> You are right. I missed that \\ is also a newline for LaTeX export.
It is a line break in any export back-end.
> Another possibility is re-purposing counter definition from ordered
> lists. Currently the "\\[@[0-9]+\\]" is used to force item number in
> ordered
Carsten Dominik writes:
> On Wed, Sep 9, 2020 at 3:06 PM Eric S Fraga wrote:
>
>> On Wednesday, 9 Sep 2020 at 14:35, Klaus Thoben wrote:
>> > Does such a function exist already? Or can somebody help me out with
>> > some Lisp code for that?
>>
>> The org agenda viewer will display timestamped e
Kyle Meyer writes:
> With Org's master (f17d301e1), the second one hangs for me with Emacs
> 26.3. Quickly stepping through org-babel-python--send-string, it
> appears to get stuck in the accept-process-output call.
>
> Using an Emacs built from master, there's no hang on my end either. If
> yo
On Wed, Sep 9, 2020 at 3:06 PM Eric S Fraga wrote:
> On Wednesday, 9 Sep 2020 at 14:35, Klaus Thoben wrote:
> > Does such a function exist already? Or can somebody help me out with
> > some Lisp code for that?
>
> The org agenda viewer will display timestamped events from all files
> listed in o
On Wednesday, 9 Sep 2020 at 14:35, Klaus Thoben wrote:
> Does such a function exist already? Or can somebody help me out with
> some Lisp code for that?
The org agenda viewer will display timestamped events from all files
listed in org-agenda-files. Set the latter and invoke the agenda
(org-agen
Hi everyone,
long time orgmode user, but never really did use the Agenda. Now, having
used Memacs quite a bit, I thought it would be handy to have an agenda
view that shows significant events related to the selected day from all
org files.
Does such a function exist already? Or can somebody help m
Thanks. I understand now.
I think to generate a patch in this case it's too much hustle, for a minor
benefit.
--
Adam
On Wed, 9 Sep 2020 at 09:13, Bastien wrote:
> Hi Adam,
>
> Adam Faryna writes:
>
> > Ok, maybe I misunderstood the purpose of this function. I wanted to
> > use it to check if
On Wednesday, 9 Sep 2020 at 10:44, Bastien wrote:
> Thanks for reporting this. Actually yes, we should consider handling
> variable-pitch-mode more pleasantly, with space-aligned tags and also
> tables that still display with fixed-width.
Also support for org-indent-mode: having the text align n
No Wayman writes:
> Bastien writes:
>
>> Hi No Wayman,
>>
>> I pushed 4f49ebb6d, a small variant of your initial patch,
>> which pass the test fine by checking whether the variables
>> are bound outside or not, ignoring them if not.
>>
>> Thanks again for the fix!
>
> Sounds good to me! Thanks,
Hi Charles,
sorry for the late feedback.
Charles Tam writes:
> I am archiving subtrees of my main Orgmode document to a top-level
> datetree in a secondary file. When I do so, I expect something like
> the following:
>
> * 2020
> *** 2020-02 February (org-odd-levels-only t)
> * 2020-02-27
Hi Nick,
thanks for reporting this, I committed a fix for this (f5573e6a0).
Best,
--
Bastien
Bastien writes:
> (In general, it would be good if downstream enhancements like these
> could be shared upstream, we are generally quite grateful for help!)
>From memory, Doom actually has a number of rather nice Org patches that
it hoards :P IIRC simply to avoid the effort of going through th
Hi Protesilaos,
Protesilaos Stavrou writes:
> Diego Zamboni [2020-09-05, 23:39 +0200]:
>
>> I had seen the same in my setup. I recently started using Doom Emacs
>> (https://github.com/hlissner/doom-emacs/) and was pleasantly surprised
>> to discover that todo and tag faces scale according to th
Hi Akater,
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.
--
Bastien
Hi Protesilaos,
Protesilaos Stavrou writes:
> 1. Run 'emacs -Q'
> 2. Open a new Org file 'C-x C-f /tmp/test.org'
> 3. Insert the following contents:
>
> * TODO this is a test :tag:
> * TODO here is another test
On Mon, Sep 07, 2020 at 10:05:38PM -0700, Samuel Wales wrote:
> well for a non-emacs application, i want to select text and capture
> using wm menu.
I routinely capture programming and UNIX history. I select text (X11
clipboard), and then I have a skel/abbrev to insert it into Emacs. I
type "pexa"
Bastien writes:
> I tested the patch and it fixes the problem just fine, I applied
> it in master as b79fef1da.
PS: Also marking this as fixed now.
--
Bastien
Hi Nicolas and Marco,
I tested the patch and it fixes the problem just fine, I applied
it in master as b79fef1da.
Thanks a lot for this!
--
Bastien
Hi Kévin,
Kévin Le Gouguec writes:
> Bastien writes:
>
>>> - Will Emacs's maintenance branch (emacs-27) be updated with Org 9.3.8,
>>> so that Emacs 27.2 includes all bugfixes for 9.3? (If so, I can open
>>> a new report on Debbugs to track this, as suggested by Stefan K.)
>>
>> Yes, thank
Hi Adam,
Adam Faryna writes:
> Ok, maybe I misunderstood the purpose of this function. I wanted to
> use it to check if the timestamp is active or inactive and I tried to
> get it by using (org-at-timestamp-p 'inactive) while pointing at the
> timestamp. But actually when I call it on any timest
D writes:
> I fully understand, though I do believe that this change is beneficial
> to the way org-forward-heading-same-level works overall, in a "principle
> of least astonishment" sort of way.
Yes, that's why I allowed this exception, but still, I think it's best
to leave the FIXME for future
Hello Vasilij,
Vasilij Schneidermann writes:
>> Thanks for the patch. I tried it and these two tests fail:
>>
>>FAILED test-org-datetree/find-date-create
>>FAILED test-org-datetree/find-iso-week-create
>>
>> Perhaps you can check the value of `org-blank-before-new-entry' and
>> inse
Ihor Radchenko writes:
>> I applied a small variant of it as a700fadd7, thanks.
>>
>> (See also the comment I added with f17d301e1, which basically means
>> that such changes are made as exceptions.)
>
> For record, the old behaviour did not only affect a single external
> package. For example, h
Hi Ian,
ian martins writes:
> Of course there's never a problem in fixing things. I'm curious how
> you did it. Will look when I have a chance.
Here it is: https://code.orgmode.org/bzg/org-mode/commit/989f50a53
Sorry I forgot to mention the commit in the ack message.
PS: As I said, it was qui
Hi Carsten,
Carsten Dominik writes:
> yes, keeping the color would be good, this can make reading these
> strings much easier.
That's what is done, as of 7a12e1499, just committed in master.
Thanks for insisting on this!
--
Bastien
47 matches
Mail list logo
