Hi Nicolas and Gustav,
Nicolas Goaziou writes:
> I'm Cc'ing Bastien because that particular point should be solved before
> any release, IMO.
Thanks for adding me to the loop.
I'll take the time today or tomorrow to understand what is at stake
here and of course, I won't release Org 9.4 before
Hi Samuel,
Samuel Wales writes:
> dunno if this is useful (probably not), but i found the following was
> necessary to fix ido.
What was the problem when refiling with ido?
> i didn't really understand it, but it fixed it.
I have tested the patch, but I'd like to understand and reproduce the
Hi Gustavo,
Gustavo Barros writes:
> I've tested it again, and I believe it is working as intended.
Thanks for confirming.
> I observe, however, a difference of behavior between
> "completing-read-default" and "ivy-completing-read" in the workings of
> "org-refile-get-location". Namely, with
Hi Ricky,
thanks for the double-check, I've now apply the change as you suggest.
Best,
--
Bastien
Hi Adam,
Adam Porter writes:
> What do you think?
I think that's a good idea to promote org-insert-subheading either by
binding it to a key or another way.
I already have some drafty code that might touch things in this (very
sensible) area, so if you don't mind, I'll come back to the details
Hi Solomon,
solomon theNinja writes:
> I'll be happy to implement exporting custom image links myself, given
> time, if that's the issue.
Sure, please go ahead! If your change is more than 15 lines or so,
you might need to sign the FSF copyright assignment:
https://orgmode.org/request-assign-
Hi Stig,
Stig Brautaset writes:
> Thank you! That did indeed do it.
Thanks for confirming...
> FWIW my stanza looks like this now:
... and sharing.
Best,
--
Bastien
stardiviner writes:
> I've already signed FSF papers before. Actually I contributed some
> patches already. :)
Argh, yes, sorry, my bad! I was confused because I saw TINYCHANGE in
previous commit messages.
--
Bastien
Hi Sebastian,
Sebastian Miele writes:
> Part of me feels that I should find a better explanation and spare you
> the trouble of figuring out what I mean. But there seems to be no
> (significantly) better explanation I can come up with without going to
> greater lengths and especially investing c
Hi Sam,
Sam Steingold writes:
> If you tell me what to do, I would gladly do it.
> I am afraid I am too busy to investigate it myself...
if you can share your .emacs file (removing private information)
I can try to bisect and find what causes Org to be loaded: you can
send it to me in private i
Hi Stardiviner,
stardiviner writes:
> Sorry for my misunderstanding. Today I re-check the org-agenda clock table. I
> found It's correct. I read this style of display wrong. :)
Okay, thanks for confirming!
--
Bastien
Hi Stardiviner,
stardiviner writes:
> About this patch, last night, I try to test ob-clojurescript eval with CIDER
> connection. But no luck, the ClojureScript REPL connection always failed to
> start. I have problem on CIDER. So I have a request that can you take a test.
> Because on my side, ~
Hi Andrew,
thanks a lot for the minimal recipe! Very helpful.
I confirm the bug and I have now (finally) fixed it.
We can close this bug from... 2013 :)
Best,
--
Bastien
Hi all,
Stig started this request more than 3 years ago:
https://github.com/github/pages-gem/pull/335
Today, GitHub does not seem to listen to this need.
If some of you care about the issue, please raise
your hand and make yourselves heard.
Thanks!
--
Bastien
Okay, I've done my home work :)
TL;DR: (1) The change is fresh, let's take the time to work together
at making it right before 9.4*; (2) the current state with the line
3216 in org-element.el is not okay; (3) let's try implementing what
Nicolas suggests wrt to attachment=>file link resolution.
*
Hi Bastien,
On Fri, Feb 14 2020, Bastien wrote:
I've revisited org-refile-get-location given your new information on
ivy-completing-read but I'm not able to see something wrong in the
current implementation of org-refile-get-location. At the same time,
I don't see why ivy-completing-read would
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bastien writes:
> stardiviner writes:
>
>> I've already signed FSF papers before. Actually I contributed some
>> patches already. :)
>
> Argh, yes, sorry, my bad! I was confused because I saw TINYCHANGE in
> previous commit messages.
It's fine,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Of course, I will raise my hand over there. Thanks for resume this up.
Bastien writes:
> Hi all,
>
> Stig started this request more than 3 years ago:
> https://github.com/github/pages-gem/pull/335
>
> Today, GitHub does not seem to listen to this
Hi Gustavo,
thanks for investigating further. From what I've seen, ivy-mode does
not set the org-refile-history variable correctly, always setting the
car of this variable to "^" after ivy-completing-read is called.
>From what I understand, this is not a bug in Org. I hope you can fix
this some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bastien writes:
> Hi Stardiviner,
>
> stardiviner writes:
>
>> About this patch, last night, I try to test ob-clojurescript eval with CIDER
>> connection. But no luck, the ClojureScript REPL connection always failed to
>> start. I have problem on
Hi Bastien,
On Fri, Feb 14 2020, Bastien wrote:
I've revisited org-refile-get-location given your new information on
ivy-completing-read but I'm not able to see something wrong in the
current implementation of org-refile-get-location. At the same time,
I don't see why ivy-completing-read would
Hi Bastien,
On Fri, Feb 14 2020, Bastien wrote:
I hope you can fix
this somehow, maybe upstream.
Unfortunately, I'm afraid I don't understand this enough, and what
'ivy-completing-read' was supposed to do, to be able to provide a
pertinent report there.
I personally don't have a problem l
Hello,
For most of my links, I want to use the ID generated by orgmode
i.e., (setq org-id-link-to-org-use-id t)
But occasionally, for targets that are not part of my agenda files, I want
to store a link of the type file:path.org::*headline
I wrote the following function to accomplish that:
(def
Hello,
Bastien writes:
> Now, I'm not sure who wants to try implementing Nicolas suggestion to
> let ox.el expand attachments into file links: since you both know the
> issue better than I do, I suggest one of you can try?
I will try to propose a patch by tomorrow evening.
Regards,
--
Nicola
Hello,
Bastien writes:
> solomon theNinja writes:
>
>> I'll be happy to implement exporting custom image links myself, given
>> time, if that's the issue.
>
> Sure, please go ahead! If your change is more than 15 lines or so,
> you might need to sign the FSF copyright assignment:
>
> https://o
On 2020-02-11, at 09:16, Bastien wrote:
> Hi Jens,
>
> it is difficult to justify existing code, it is easier to answer to
> bug reports. If you think there is a bug in this aread, can you tell
> what it is?
Hi Bastien,
many thanks for following up on this!
I see two or more bugs:
1. Export t
On 2020-02-11, at 16:40, Bastien wrote:
> Matt Price writes:
>
>> However, at least one very common syntax highlighter, https://
>> highlinghtjs.org, expects just a single tag, as do other
>> common CSS frameworks. These often leave odd borders or background
>> color disruptions which somewhat d
Alright, I'll wait. Meanwhile I have a few crude advises in my config that
allow some functionality, so no hurry :)
On Fri, Feb 14, 2020 at 7:17 PM Nicolas Goaziou
wrote:
> Hello,
>
> Bastien writes:
>
> > solomon theNinja writes:
> >
> >> I'll be happy to implement exporting custom image link
Hello,
Jens Lechtenboerger writes:
> 1. Export to HTML when the title contains markup, say this one:
>
> #+TITLE: This does *not* work
What does not work?
> The HTML title element contains a nested b element, which is
> invalid as only text is allowed.
Who said that? The above is perfectly va
Completing myself,
Nicolas Goaziou writes:
> General export rules are described in ox.el (org-export-options-alist),
> then each export back-end define its own specificities (look at the
> back-end definition).
This doesn't mean the manual cannot be improved, of course. Improvements
are welcome
Also, it would be nice to get access to the "info" variable for custom
links;
that way, custom image links could handle attributes like "#+WIDTH".
But straight up giving the ":export" function (registered through
"org-link-set-parameters")
another argument would break all existing custom links, so
Nicolas Goaziou writes:
>> Now, I'm not sure who wants to try implementing Nicolas suggestion to
>> let ox.el expand attachments into file links: since you both know the
>> issue better than I do, I suggest one of you can try?
>
> I will try to propose a patch by tomorrow evening.
Thanks!
If th
Hi Jens,
Jens Lechtenboerger writes:
> that issue has been resolved:
> https://lists.gnu.org/archive/html/emacs-orgmode/2019-10/msg00099.html
great, thanks for confirming.
--
Bastien
stardiviner writes:
> I use CIDER (sesman) keybinding =[C-c C-s d]= on ob-clojure src
> block to link current buffer directory to CIDER REPL session.
I simply start Cider with C-c M-j and then execute the Clojure source
block with C-c C-c, it works fine.
> I guess this should work for ClojureSc
Hi Nicolas,
Nicolas Goaziou writes:
> This doesn't mean the manual cannot be improved, of course. Improvements
> are welcome in that area.
I see org-export-options-alist is not mentioned in the manual - would
it be worth mentioning it in the "Adding Export Back-ends" section?
--
Bastien
We have a good reference documentation for creating export backends:
https://orgmode.org/worg/dev/org-export-reference.html
But we *badly* need a step by step tutorial on Worg.
Anyone would like to volunteer for writing such a tutorial?
--
Bastien
Stig Brautaset writes:
> Hi Bastien,
>
> Bastien writes:
>>> I can easily do this in the list of TODOs, with a tag search. However, I
>>> haven't figured out how to do this for the agenda. Is it possible? If
>>> so, how?
>>
>> From what I understand, check `org-agenda-tag-filter' to see how to
>
I have no compelling reason to delete those lines, it just sometimes happens
that I do delete when I do a quick capture, and then they wreak havoc in my
main org buffer. No longer, thanks to you!
Miguel
On Tue, 11 Feb 2020 at 11:38 WET, Bastien wrote:
> Hi Miguel,
>
> Miguel Morin writes:
>
I wonder if it would make sense to use shadow-cljs rather than cider as
a back end for evaluating clojurescript?
More generally, I wonder if there would be any benefit in considering a
Clojure CLI Tools back end integration and bypassing CIDER altogether?
While I love CIDER, I'm not sure it is t
In Doom Emacs (https://github.com/hlissner/doom-emacs), Org's babel
packages aren't loaded all at once with org-babel-do-load-languages, but on
demand when their src blocks are encountered (fontified) or executed. Same
with its export backends.
Dooms maintainer, Henrik Lissner, has kindly extracte
On 2020-02-14, at 20:31, Nicolas Goaziou wrote:
> Hello,
>
> Jens Lechtenboerger writes:
>
>> 1. Export to HTML when the title contains markup, say this one:
>>
>> #+TITLE: This does *not* work
>
> What does not work?
>
>> The HTML title element contains a nested b element, which is
>> invalid as
41 matches
Mail list logo
