Bastien writes:
> 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?
The primary source of
Hi Bastien,
Bastien writes:
> Christian Schwarzgruber writes:
>
>> The question is now, is it possible to further reduce the advised
>> functions to just one advised function.
>
> I am sorry, I don't understand what change does it imply on Org's
> side. Can you explain us a bit more?
Nothing
Hi Miguel,
Miguel Morin writes:
> 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!
Glad the change can still whatever habits you have.
Best,
Thank you Bastien,
You are welcome, I have never gotten around to sign the FSF papers as
I thought it was a
bit of a hassle, but with those clear instructions I have now started
the process. I guess
I have to wait until the process is done until I can resubmit?
On Wed, Feb 12, 2020 at 6:31 PM
Hi Stig, Marcin, Jean-Christophe and Robert,
Stig Brautaset writes:
> The primary source of `ox-jira.el' was once[1] an Org tutorial (to
> myself) for creating an Org export backend. If this is broadly what you
> had in mind, I can dig that out of Git history and put it on Worg.
Yes, I think
> On Feb 16, 2020, at 17:05, Marcin Borkowski wrote:
>
>
> On 2020-02-16, at 01:46, Jean-Christophe Helary
> wrote:
>
>>> On Feb 16, 2020, at 2:55, Marcin Borkowski wrote:
>>>
>>>
>>> On 2020-02-14, at 21:48, Bastien wrote:
>>>
We have a good reference documentation for creating
Hello,
Kyle Meyer writes:
> It looks like a good direction to go.
Thank you for the feedback!
I fixed the various typos you mentioned.
> As far as I can see (by looking at the diff and quickly testing), the
> file+{sys,emacs} functionality is being removed. That's probably
> okay/intended,
On 2020-02-16, at 01:46, Jean-Christophe Helary
wrote:
>> On Feb 16, 2020, at 2:55, Marcin Borkowski wrote:
>>
>>
>> On 2020-02-14, at 21:48, Bastien wrote:
>>
>>> We have a good reference documentation for creating export backends:
>>> https://orgmode.org/worg/dev/org-export-reference.html
Hi Nicolas,
Nicolas Goaziou writes:
> I don't think so. It is a constant, which may only matter when you write
> an export-backend. Its value is not even particularly important since
> any back-end can ignore it. Only its syntax really matters, as pointed
> out in, e.g.,
Hi Nicolas,
Nicolas Goaziou writes:
> This is the first part of the suggested changes. These do not touch
> attachment modifications, but rather improve the tooling in "ol.el".
Thanks for working on this--and Kyle for the careful review.
> `org-link-parameters' accepts a new property, :open,
non-leaf olpaths are not usefully considered to be directories in my
opinion. all olpaths should be equal in status.
On 2/16/20, Samuel Wales wrote:
> On 2/14/20, Bastien wrote:
>> What was the problem when refiling with ido?
>
> idk if the following will be useful but here goes.
>
> bear in
Hi there!
On 2020-02-15, at 15:02, Nicolas Goaziou wrote:
> Jens Lechtenboerger writes:
>
>> the W3C Markup Validator [1] disagrees with this output from
>> ox-html (which I reduced to the essential parts):
>
> OK. I was talking about the Org syntax. I misread your initial report.
>
> I won't
Thanks for the response and work Bastien. I will check out the updated
version when I get a chance.
One point possibly relevant with regards to Clojurescript. I suspect
there could be a reasonable use case when you consider clojurescipt in
the context of node rather than just as a browser
Hi Nicolas,
Nicolas Goaziou writes:
> That is subconscious, actually. I considered removing them,
> then hesitated, and it all ended up in an intermediate state. Removing
> it properly would require to remove :application property in the parser,
> too. At some point, this functionality needs to
Hi Samuel,
Samuel Wales writes:
> If you can't reproduce witn your ido settings, I'll try to
> provide an MCE at some point.
I don't use ido-mode, so I don't have any ido setting and It's
difficult for me to both understand and chase the bug.
I suggest you start by checking the bug is still
Bastien,
Thanks for the reply. I’ll look into it. However, I’d initially ruled that
out because the final output is meant to be an image. So, to get just text
insertion into the html output I imagine would be a bit of a hack. For
instance what to set image-converter to etc.
Matt
On Sun, Feb 16,
Hi Gustavo,
Gustavo Barros writes:
> But the fact that
> 'completing-read-default' returns the refile location with a double
> trailing slash makes me think there is still something to be fixed in
> 'org-refile-get-location'.
if you're not tired of the hunt, please tell us when you find
Hi Terje,
Terje Larsen writes:
> You are welcome, I have never gotten around to sign the FSF papers as
> I thought it was a
> bit of a hassle, but with those clear instructions I have now started
> the process.
Thanks!
> I guess I have to wait until the process is done until I can
> resubmit?
Hi Matt,
Matt Huszagh writes:
> The patch below allow's you to provide your own shell command the
> generates HTML from a latex fragment and places the output directly in
> the exported HTML file.
Can you get the same output by configuring a new symbol in
`org-preview-latex-process-alist' then
On 2/14/20, Bastien wrote:
> What was the problem when refiling with ido?
idk if the following will be useful but here goes.
bear in mind this was a while back. this is partly from memory.
i don't know if the fix fixed all of them, but it definitely seemed
to, at least with my ido settings.
your quote is from a many years old report. i was providing it in
case it was useful historically.
--
The Kafka Pandemic
What is misopathy?
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
Hi Christian,
you might want to have a look at org-agenda-finalize-hook, though I'm
not sure it can help, I'm not familiar with org-super-agenda enough.
HTH,
--
Bastien
Hi Uros,
Uros Perisic writes:
> I think this would make the org-mode literate programming experience
> significantly smoother.
>
> Any thoughts on including this in org-mode?
This looks like a good idea. We are close to releasing 9.4, so it too
late for this release, but feel free to send a
Hi Tim,
thanks for your email.
Tim Cross writes:
> I wonder if it would make sense to use shadow-cljs rather than cider as
> a back end for evaluating clojurescript?
I am inclined to question the usefulness of evaluating ClojureScript
code *at all*.
> More generally, I wonder if there would
Tim Cross writes:
> Thanks for the response and work Bastien. I will check out the updated
> version when I get a chance.
Thanks.
> One point possibly relevant with regards to Clojurescript. I suspect
> there could be a reasonable use case when you consider clojurescipt in
> the context of
Matt Huszagh writes:
> Thanks for the reply. I’ll look into it. However, I’d initially ruled
> that out because the final output is meant to be an image. So, to get
> just text insertion into the html output I imagine would be a bit of
> a hack. For instance what to set image-converter to etc.
Hi Samuel,
sorry to insist, but what I really need is a *fiable and easy* way to
reproduce a bug. Other comments (like code analysis) are only useful
when I do have a reproducible bug.
I'm willing to spend as much time as needed on a MCE, but I'm waiting
for this MCE before interpreting
Hi Matt,
Matt Huszagh writes:
> Thanks for the feedback. I've filled out the form you sent and sent it
> to the email listed.
Thanks! It looks good.
Let me know when you get the answer from the FSF.
If you don't in four weeks, please ping them again cc'ing me.
--
Bastien
Will do, thanks!
On Sun, Feb 16, 2020 at 5:10 PM Bastien wrote:
> Hi Matt,
>
> Matt Huszagh writes:
>
> > Thanks for the feedback. I've filled out the form you sent and sent it
> > to the email listed.
>
> Thanks! It looks good.
>
> Let me know when you get the answer from the FSF.
>
> If you
Hi all,
After hours of frustration ending in a realization that I should really
just read the change logs, I tracked down the reason why editing
source blocks was now destroying my window layout. I restored the
old behavior hidden behind a custom variable. Let me know if it looks
ok, or if more
Hi Tom,
Tom Gillespie writes:
> Hi all,
> After hours of frustration ending in a realization that I should really
> just read the change logs, I tracked down the reason why editing
> source blocks was now destroying my window layout. I restored the
> old behavior hidden behind a custom
Hi Kyle,
Thank you for the pointer. That does indeed solve my issue. I must
have missed it because it wasn't merged into maint. The conversation
in that thread seems to indicate that the old behavior is the correct
default. I imagine that there might be a few other folks with Matt's
use case,
i found a note that says that there isa nother disticnitont hat was
causing the bugs: a distinction between the current file and
non-current file.
it wreaks havoc to make that distinction.
* REF this works around the bugs
=this is in my personal patches
vvv
Modified
Hi Matt,
Matt Huszagh writes:
> From 056d23d9e5caa6fc22907014e0128519fcc84b6e Mon Sep 17 00:00:00 2001
> From: Matt Huszagh
> Date: Sat, 15 Feb 2020 18:42:11 -0800
> Subject: [PATCH] add custom command option when converting latex fragments to
> html
>
> This allows you to set a custom
Hi Bastien,
On Sun, Feb 16 2020, Bastien wrote:
Hi Gustavo,
Gustavo Barros writes:
But the fact that
'completing-read-default' returns the refile location with a double
trailing slash makes me think there is still something to be fixed in
'org-refile-get-location'.
if you're not tired of
Thanks for the feedback. I've filled out the form you sent and sent it
to the email listed.
Adjusted patch below. I didn't add a value to the customization. I'm
honestly not very familiar with the customize interface since I never
use it. Is that a default value if the user selects string from
On 2/16/20, Bastien wrote:
> I'm willing to spend as much time as needed on a MCE, but I'm waiting
> for this MCE before interpreting comments on code and possible bugs.
i see.
fyi i was not specifically trying to report a bug or supply an mce.
instead, i was hoping only to contribute to
Looks like a bug in ein,
https://github.com/millejoh/emacs-ipython-notebook/issues/668
On Fri, 14 Feb 2020 at 05:03, Bastien wrote:
>
> 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
Hi Sam,
Sam Steingold writes:
> Looks like a bug in ein,
> https://github.com/millejoh/emacs-ipython-notebook/issues/668
Thanks for the follow-up.
I looked at ein-notebooklist.el a bit, where I could not understand
why logging in would call org--setup-calendar-bindings but I don't
know ein
Hi Michael,
Michael Wu writes:
> In the following block:
>
> #+BEGIN_SRC python :results value :session
> def f():
> return 5
> f()
> #+END_SRC
>
> It gives the message
>
> "Code block returned no value"
I cannot reproduce this bug with latest Org from the master branch.
If you can, let me
40 matches
Mail list logo
