Hi Nick,
Nick Savage writes:
> I've attached a patch to address this.
Applied in maint, thanks a lot!
--
Bastien
on master. For bug fixes, please make patches
againt the maint branch.
Thanks!
PS: While Org 9.5 is (slowly) maturing, we will have time to release yet
another bugfix release.
--
Bastien
t figure out what was
causing this.
org-mac-link.el lives in https://git.sr.ht/~bzg/org-contrib and
we make no promise on whether it's compatible with Org's core.
I'm closing this now.
--
Bastien
all of
> "org-contrib" currently is "Org-mode Babel support for Arduino".
>
> Please add "org-contrib.el" containing some juicy metadata.
Well, I don't know if they are *that* juicy but I just added some.
Let me know how this look! And thanks for the above instructions,
that's very useful.
Best,
--
Bastien
Hi Victor,
"Victor A. Stoichita" writes:
> Le 03 May 2021, Bastien a écrit :
>> I suggest a criterium for keeping ob*.el files in Org could be that
>> the extension is known by Emacs _or_ that the supported language is
>> well-established.
>
> I happe
lock).
... which is good if the package is really maintained, and calling for
trouble if it is not. Anyway, I agree with you about the importance
of ob-lilypond.el.
Best,
--
Bastien
e
so that I can you as the maintainer.
Best,
--
Bastien
slash was
> appended at the end of every path, but candidates were stored in
> `org-refile-history' without that extra slash. Bastien took care of
> that and indeed changed things so as to pass the elements to
> `org-refile-history' with the trailing slash as appropriate.
>
&
e ob-*.el for which we don't have a
maintainer or we are not 100% sure they are compatible. But luckily
enough, I don't think backward compatibility problems happen often
with Babel files.
--
Bastien
> Which is correct.
>
> Then both display in agenda of <2020-02-01>.
> Which is not correct for 'delay all occurences'.
> It should display in agenda of <2020-02-02>.
I'm just bumping this thread because this issue is still open, I'll
review it before Org 9.5.
--
Bastien
Hi Gustavo,
well, clearly my mind is dull right now - I pushed another better fix,
but please report any better solution if you have one.
Thanks!
--
Bastien
for stating it more directly than I did.
--
Bastien
uld like maintainance to happen elsewhere than in Org's core.
--
Bastien
led up, hiding the top of the buffer, even though there is no lack
> of space in the frame to fit the whole window.
Fixed in maint, thanks.
--
Bastien
Hi Steven,
"Steven Bagley" writes:
> Yes, that works for the example I quoted. The source of the original
> "::" is org-mac-link, not my typing. Maybe that could insert a
> different character sequence to avoid any confusion.
can you propose a patch for this?
--
Bastien
ob-groovy.el, I believe Groovy is quite actively used out there.
But I'll add these three to the "maybe" list.
Thanks,
--
Bastien
Hi Mingkai,
thanks a lot for the analysis and the diff, it helps a lot.
I pushed this change:
https://code.orgmode.org/bzg/org-mode/commit/dfdd5cd0
Keeping the headline numbering consistent with the TOC numbering seems
the right thing to do here.
Thanks!
--
Bastien
ning 2)
> (match-end 0)))
Here and for the rest of the patch: please try to keep lines below 80
characters. I'm aware this is not always feasible, especially given
long functions with many nested s-exps, but let's try to come as close
as possible to 80.
Thanks!
--
Bastien
ec6d1df9b, together with tiny changes in
the commit message.
Thanks!
--
Bastien
ort.
Thanks!
--
Bastien
ifference by comparing the relevant HTML
portion before and after this change?
--
Bastien
it's just that maintainance will be easier outside.)
Are there any other?
I'll leave this thread open during this week, no need to rush here.
Thanks,
--
Bastien
Bastien writes:
> Bastien writes:
>
>> The files previously stored in the contrib/ directory of Org's repo
>> now lives here: https://git.sr.ht/~bzg/org-contrib
>
> Let's announce this change on https://updates.orgmode.org.
For good! (Sorry for the noise.)
--
Bastien
Bastien writes:
> By merging `org-speed-commands-default' and `org-speed-commands-user'
> into a single `org-speed-commands' option, we make this possible, but
> this change will ignore people's `org-speed-commands-user' config, so
> this is a breaking change.
I've done so with com
catching this, the careful analysis and the patch.
Applied to the maint branch.
Thanks,
--
Bastien
Eric S Fraga writes:
> On Monday, 3 May 2021 at 15:00, Bastien wrote:
>> Applied with commit 479a3da22 in master, thanks.
>
> Thank you Bastien. However, as soon as I looked, I realised that my
> commit message missed out the "doc/" part of the file name fo
st) patch and report any problem?
Thanks for your patience in testing this!
--
Bastien
diff --git a/lisp/org.el b/lisp/org.el
index c0b5ee5ec..c20539a8a 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -18846,17 +18846,6 @@ ELEMENT."
(t
(goto-char start)
(current-indentation
- (
Applied with commit 479a3da22 in master, thanks.
--
Bastien
Hi Tim,
Tim Visher writes:
> Here's a quick patch that fixes that up:
Applied, thanks. If you want to contribute more to Worg, please
send me the username you want in private and I'll create an account
for you on code.orgmode.org.
Thanks!
--
Bastien
Bastien writes:
> The files previously stored in the contrib/ directory of Org's repo
> now lives here: https://git.sr.ht/~bzg/org-contrib
Let's announce this change on https://updates.orgmode.org.
--
Bastien
.
Files in https://git.sr.ht/~bzg/org-contrib need new maintainers:
if you want to maintain one of these files (outside of the repo),
please contact me directly.
The plan is to build a NonGNU ELPA package called "org-contrib",
we will see if that's feasible.
Thanks,
--
Bastien
s make sense would be to support [ ]/[X] on top of
the already supported [0%]/[100%] and [0/n]/[n/n].
What do you think? (I tried your mode and unless I didn't try it
correctly, it does not seem to do that.)
Thanks,
--
Bastien
Hi Jeremie,
I pushed a fix for this (though a little bit before I read your public
message here) - let me know if it needs to be enhanced.
Thanks!
--
Bastien
nks.
> Sorry for just dumping all these nits at your front door Bastien I
> should at least write test cases for them. Will try to find the time
> Sometime Later™.
This might help: https://orgmode.org/worg/org-faq.html#indentation
Thanks!
--
Bastien
e's anything I can do to help get it applied.
Applied in Worg, thanks a lot.
--
Bastien
]
>
> 3. You can't follow the link using mouse-left because of the "::" in
> the link, which makes that line into an org "description list
> item". The message is "No link found".
Confirmed, thanks for the reproducible recipe.
--
Bastien
Nick Daly writes:
> Yes, I can confirm that `org-babel-plantuml-post-process` is not
> necessary for the second patch. That was a line accidentally left over
> from the first, larger, patch.
Thanks Nick for confirming.
--
Bastien
Hi Ihor,
Ihor Radchenko writes:
> I can reproduce. The issue appears only in level 1 headlines because of
> wrong regexp in font-lock-keywords. The attach patch should fix the
> problem.
Applied in maint, thanks a lot!
--
Bastien
Hi Nick,
Nick Savage writes:
> The attached patch ensures the behaviour is correct when
> `global-visual-line-mode' is enabled and that there are no behaviour
> changes when it has not already been enabled.
Applied in maint with commit cb0ef1280. Thanks!
--
Bastien
Hi Ihor,
applied in maint as commit 0e7153e63, thank you very much!
--
Bastien
Bastien writes:
> I suggest (setq org-adapt-indentation 'headline-data).
With electric-indent-mode turned off, that is.
--
Bastien
n is t
>
> * Heading
> :PROPERTIES:
> :ARCHIVE: new
> :END:
>
> But if org-adapt-indentation is nil, it will be like:
>
> * Heading
> :PROPERTIES:
> :ARCHIVE: new
> :END:
I suggest (setq org-adapt-indentation 'headline-data).
--
Bastien
in this case.
> For default values, a distance of one blank line is ensured to the
> next heading.
My understanding is that `org-blank-before-new-entry' will ensure
there is a blank line before the new entry, which is what I see.
Let me know if there is something I miss here. Thanks!
--
Bastien
of the markers was somehow demanded.
Yes, this came to my mind too, but I will refrain from adding this
new toggling capability for emphasis markers until people convince
us it has to be implemented.
--
Bastien
sion of the
patch. So the change won't be that "breaking" but let's still assess
whether it will break many configurations.
Thanks,
--
Bastien
might surprise users.
Indentation is quite sensitive: what do you think of setting a new
default value of nil for `org-adapt-indentation' in Org 9.5?
--
Bastien
, we make this possible, but
this change will ignore people's `org-speed-commands-user' config, so
this is a breaking change.
Do you think this change could be too sensitive for users?
--
Bastien
Hi Yasushi,
Yasushi SHOJI writes:
> I see a plain list unfolded when I cycle a sub headline.
Fixed in maint with commit 5021bada9, thanks again for reporting this.
--
Bastien
Hi Damien and Jeremie,
Jeremie Juste writes:
> The following patch will at least harmonize the results towards the
> data.frame.
I see the patch has been applied - thanks!
I'm marking this bug as resolved right now, feel free to reopen it if
I'm wrong.
Thanks,
--
Bastien
about |
> | proposed project. |
>
> it results in an error message "Not in table data field".
Fixed in maint with commit eedbe286e, thanks again for reporting this.
--
Bastien
maybe it was intended ?
>
> Nicolas Goaziou wrote this test, perhaps he could comment on this.
Sure, feel free to adapt the code further if needed after discussing
this.
Thanks,
--
Bastien
Hi Caio,
Bastien writes:
> thanks for reporting this -- it seems to be a variant of what Gustavo
> has been reporting in this thread:
>
> https://orgmode.org/list/87a6zkv3m2@gmail.com/
>
> ... for which I don't have a solution yet. I'm confirming this bug
> for https:
commit ccd513a3c, thanks!
--
Bastien
Kyle Meyer writes:
> Kyle Meyer writes:
>
>> Ah, sorry for not writing that more clearly. By the above, I wasn't
>> saying that the ones I commented on were the _only_ ones I see with
>> Emacs 24.5 on maint.
>
> I've dealt with a few more.
Thank you both very much!
--
Bastien
Timothy writes:
> I think it makes sense to leave this open until a fix has been
> applied.
Done, thanks.
--
Bastien
create histograms.
I'm closing this bug now - feel free to reopen it if I misunderstood
the thread.
--
Bastien
Hi,
Bastien writes:
> Indeed, I can reproduce this bug with latest Org.
FWIW I cannot reproduce this anymore (with latest Org and Emacs),
I'm closing this bug now.
Feel free to reopen it if necessary.
--
Bastien
Bastien writes:
> Applied in maint with commit 0a8079b4d, thanks a lot!
Er, sorry, I should have explained why I applied it to maint too,
on top of applying it to master three days ago: first of all, this
is a bugfix, and I also want to take the opportunity of releasing
Org 9.4.6 so that m
u can configure git send-mail to send a patch to the list
as an email and then we can discuss the explanation part that you can
add after the change log part.
Thanks,
--
Bastien
Applied in maint with commit 0a8079b4d, thanks a lot!
Ihor Radchenko writes:
> Bastien writes:
>
>> Can you provide a patch for this?
>
> Sure. Attached.
--
Bastien
on the org-link
invisible property specs.
In any case, I don't think `org-toggle-link-display' should display
emphasis markers.
--
Bastien
I don't see a strong reason to hard-code the set of speedy
keys. See the attached patch, which proposes to use just one option
`org-speed-commands'.
This would be a breaking change, but I don't think we do otherwise.
Would this suit your needs? What do you think about the change?
--
Bastien
diff
I thought applying this first patch would
help clarify the discussion on this other thread, as the problem is
different.
I let you and Nicolas move forward on separators guessing, because so
far I'm not really convinved Org should try to be too clever here.
Thanks,
--
Bastien
sted.
Fixed with commit fb3030188 in the maint branch, thanks a lot.
Please test it and report any problem you may encounter.
Thanks,
--
Bastien
Hi Gustavo,
sorry for the slow reply.
I applied this patch in master with commit e8562a332.
Thanks!
--
Bastien
Hi tumashu,
tumashu writes:
> This is v2 patch, use completing-read-multipul.
Thanks for the patch. You can already do this:
(setq org-use-fast-tag-selection nil)
Then you'll be able to select tags the way you implemented it
with this simple mode.
--
Bastien
:
FAILED ob-tangle/block-order
FAILED ob-tangle/continued-code-blocks-w-noweb-ref
Let me know if you manage to pass all the test (or fix them...) and
silent the warning.
Thanks!
--
Bastien
Hi Alan,
"Alan D. Salewski" writes:
> Sure thing; included below.
Applied in master as commit a2403321a, thanks!
--
Bastien
er. The patch for master attached.
--
Bastien
Hi Richard,
thanks for this addition!
I think ":refile-targets" is more straightforward. I applied your
patch with this change and a slightly modified commit message. Also,
I documented this in the manual and added an entry to etc/ORG-NEWS.
Thanks!
--
Bastien
Hi Timothy,
Timothy writes:
> I think there's potential for some really nice experiences leveraging
> Org's latex rendering in combination with some languages' symbolic maths
> ability.
Applied in master as commit b90b850ae.
Can you add a etc/ORG-NEWS entry for this?
--
Bastien
Timothy writes:
> Hi pillule, should we consider this patch cancelled?
It is already :)
--
Bastien
essage - see this explanations:
https://orgmode.org/worg/org-contribute.html#commit-messages
Let us know if you need more directions and how to produce a patch
that we can more easily apply.
Thanks!
--
Bastien
Hi Nick,
Nick Daly writes:
> +(org-babel-plantuml-post-process out-file)
Note that I had to remove the line above from your second patch.
Can you confirm it is not necessary for your second patch to work?
Thanks,
--
Bastien
adding another keybinding to the agenda especially
since there is no keybinding for `org-priority-show'.
Thanks,
--
Bastien
Hi Ivan,
thanks for the explanations. I applied your patch in maint with
commit 45ca597f9, adding a commit message to it.
See https://orgmode.org/worg/org-contribute.html#commit-messages
Thanks,
--
Bastien
Hi Emily,
thanks for the patch and sorry to reactivate this old thread.
Did you find time to make the tests and, perhaps, to update the patch?
Please let us know - thanks!
--
Bastien
but I'd also love to hear from other macro
users here, and I'll definitely follow your call here.
--
Bastien
Nicolas Goaziou writes:
> So, maybe it is a bit early to close it.
Okay, thanks for the heads up, I'm reopening then.
--
Bastien
/928e67df
> org-protocol: Allow slashes after sub-protocol
I'm optimistically closing this patch. If the OP confirmes it is
still needed and Maxim confirms it is correct, we can apply a new
one.
Thanks,
--
Bastien
Hi Timothy,
Timothy writes:
> The latest in my visually-oriented (mostly) short patch series, adding
> basic fontification to inline export snippets --- @@comment:these
> things@@.
Applied in master with commit eef9027c, thanks! I also added a note
in etc/ORG-NEWS.
--
Bastien
Applied in maint as commit 400d2d9fd, with a minor modification of the
commit message. Thanks!
--
Bastien
Hi Alan,
applied in master as commit 9aa9f3b1f.
Thanks you very much!
Can you announce this by providing a patch for etc/ORG-NEWS?
--
Bastien
into
> exported documents is a mistake.
FWIW I also think inserting Javascript in HTML export is wrong.
Commit bb24248b8 turns `org-html-head-include-scripts' to nil by
default, I advertized the change in etc/ORG-NEWS.
> Bastien: You certainly have my permission to use my
> CodeHigh
e this alternative, simpler, patch. It just adds a flag that,
> when enabled, runs for SVG images exported via PlantUML.
Yes, I think the smallest change here is better, we'll see if others
want to the bigger one later on.
Applied as commit 7da20ff21, with some small modifications, thanks.
--
Bastien
Eric S Fraga writes:
> On Saturday, 1 May 2021 at 08:56, Bastien wrote:
>> I have fixed this with commit ee507de47, can you confirm?
>
> Seems to work just fine now. Thank you.
Thanks for confirming!
--
Bastien
5, thanks.
Please see the commit changelog for future patches:
https://code.orgmode.org/bzg/org-mode/commit/7c99d1555
Also https://orgmode.org/worg/org-contribute.html#commit-messages give
more detailed directions.
Thanks,
--
Bastien
it.
Thanks,
--
Bastien
; on a table.
I have fixed this with commit ee507de47, can you confirm?
Thanks,
--
Bastien
Hi Nicolas,
Nicolas Goaziou writes:
> This post is an update about "wip-cite-new" branch, which I rebased
> a few minutes ago.
I'm attaching a call for help to this thread so that more people can
test this before we merge it into master.
Thanks again for this important work!
--
Bastien
Eric S Fraga writes:
> I get this when I try:
Thanks - I see what's wrong, I'll fix it.
--
Bastien
Hi Timothy,
TEC writes:
> * Error: Element p not allowed as child of element h2 in this
> context
> Org currently seems to put a p.subtitle inside the heading.
> This violates the "phrasing content" restriction.
>
>
Thanks for reporting - Tim can you double-check this?
--
Bastien
> In org-display-inline-images:
> org.el:16554:57:Warning: reference to free variable ‘image-map’
could you provide a patch for these two warnings for the maint branch?
--
Bastien
ise, I'll announce this in
the release notes.
--
Bastien
ix problems.
Anyway, glad to have your input/patches on org-protocol.el anyway.
Thanks,
--
Bastien
I allowed myself to shortene the commit message a little bit, avoiding
personal statements ("as I think").
Also note that this patch did not land on updates.orgmode.org because
it was sent as a reply - I'll try to fix Woof! here.
Thanks,
--
Bastien
shifting org-src--{goto-}coordinates
> to a point-based approach from a column-based approach, and it seems to
> have fixed the problem.
Can someone else please test this patch and report any possible problem?
I guess tests come a bit short for such fixes.
Thanks,
--
Bastien
to do, what happens
instead, and how the patch fixes the problem?
Thanks,
--
Bastien
t; seems fine.
Indeed, thanks Arne for reporting this.
> Also, a bit downstream I see
>
> (if (not pubdate0) "" ;; Skip entries with no PUBDATE prop
>
> It seems like this should be updated to look at pubdate rather than
> pubdate0 to avoid "nil" for the empty string
> case.
Indeed too. Applied as commit 8ab1e30db in maint.
Thanks,
--
Bastien
701 - 800 of 9927 matches
Mail list logo
