Hi Timothy,
> This is moving at a glacial pace, but I'd love to see this merged ---
> there's clearly a lot of interest in this from the community if not
> within this mailing list (ob-async which is more limited has 250 stars
> on GitHub).
Yes, this has taken far too long -- sorry about that.
T
Hi Timothy,
thanks for your answer and your willingness to help here, much
appreciated.
Timothy writes:
> I also think that regardless it would be good to put out a call asking
> if anyone else is interested/willing to do this: I'm going to be busy
> sometimes, a reduced workload is clearly pre
Hi Tim,
Tim Cross writes:
> I agree and am willing to help if I can.
Great! Would you agree to be "officially" appointed to this role,
with Timothy? I put quotes on "officially": when moving toward the
new maintainance team, I'd like to list maintainers and their roles,
including the "contrib
Hi Everyone,
This is a very me-centric email, but I've got a collection patches that
have received little attention (1 of the past 9 patches I've submitted
has been reviewed by a core contributor, 6 have zero replies). I care
about them, and I think it would be good if they were looked at.
So, I'
Hi All,
I think there's potential for some really nice experiences leveraging
Org's latex rendering in combination with some languages' symbolic maths
ability.
This is /very nearly/ already supported, `org-babel-result-end' just
needs to be tweaked to also remove LaTeX environment -type #+results
Hi all,
we are looking for someone to take charge of a very important task:
reproducing bugs reported on this list.
Bug reports generally starts with "Bug: " in the email subject, even
if some emails directly sent to the list may omit this keyword.
Once you confirm a bug, you would need to reply
On Sat, Apr 24, 2021 at 11:44 PM Timothy wrote:
>
> This was not marked as applied on updates.orgmode.org.
> Doing so with the X-Woof-Patch header.
>
> ian martins writes:
>
> > Thanks. And thanks for taking the time to fix issues that you find. It
> > continues to improve because of your contri
On 21/03/2021 05:46, Samuel Wales wrote:
the issue is that when i click on google, the space before "hi" does
not show up in the earch box. ergo, different results.
*** should be orig
[[http://www.google.com/search?q=%7E%22retroactive%20whatever%22%20%22hi%22][retro
original]]
*** should be fix
Hi Nick,
sorry for the late reply.
Nick Savage writes:
> I'm willing to volunteer to maintain ob-sqlite.el. I think like Andy,
> I have some work to do to get up to speed on my elisp but I'm
> comfortable enough with sqlite itself.
I added you as the ob-sqlite.el maintainer in 55ef8e858.
I'll
Hi Andy,
Andy Klock writes:
> Can I throw my hat in to help maintain ob-sql.el ?
Are you still considering it? That would help, and it comes with no
obligation, since everyone here is on best-effort mode.
Hi Maxim,
Maxim Nikulin writes:
> For a while, improvement is significant, so I am attaching the patch
> that should make jumps using org-goto or org-refile faster. I hope, I
> have not broken anything.
Thanks a lot for the patch.
Are you still using it? Did anyone tested it?
Hi Frederic,
Frederic Santos writes:
> It looks like the PDF manual for Org mode is no longer available
> (https://www.gnu.org/software/emacs/manual/org.html): only the html
> version is online now.
> Do you know why? And will the PDF version be back someday?
The PDF manual is still here: https
I gave this a try and it works for me. One thing I noticed is that if you
run a call asynchronously, the final result ends up under the source block
instead of the call. In the example below both RESULTS were written after
I ran the call.
#+name: test-call
#+begin_src python :results outp
On Sun, Apr 25, 2021 at 1:55 AM András Simonyi wrote:
>
> Dear All,
>
> my 2c on this issue: citeproc-el supports per cite author suppression
> under the hood, but citeproc-org always maps "suppress author" mode
> citations to suppressing only the first cite, because my impression
> was also that
Bastien,
> I hope this is not confusing.
no, that's perfectly clear. thanks.
Greg
Timothy,
interesting. would this show up in #+RESULTS blocks? in (heaven
forbid!) #+BEGIN_SRC blocks?
cheers, Greg
Hi Stefan,
Stefan Kangas writes:
> The above feature request for `org-html-htmlize-region-for-paste' has
> been sitting in the Emacs bug tracker for 10 years. It seems like no
> one on our side has taken an interest in it.
Yes, this is quite a long-standing issue, and I for one did not have
en
Bastien writes:
> Hi Stefan,
>
> Stefan Kangas writes:
>
>> The above feature request for `org-html-htmlize-region-for-paste' has
>> been sitting in the Emacs bug tracker for 10 years. It seems like no
>> one on our side has taken an interest in it.
>
> Yes, this is quite a long-standing issu
Hi Ihor,
Ihor Radchenko writes:
>> Thanks, but you forgot the note to etc/ORG-NEWS announcing the new
>> option la mission.
>
> Do I miss something or the need to add ORG-NEWS entry is not mentioned
> in the contribution page?
I updated https://orgmode.org/worg/org-contribute.html to mention
et
Hi Warren,
Warren Lynn writes:
> With org-mode 9.4, if you have a repeated task like this:
>
> * TODO My weekly task
> SCHEDULED: <2020-10-14 Wed +1w>
>
> In daily agenda, if you mark the task done, which will cause the
> above to change into:
>
> * TODO My weekly task
> SCHEDULED: <2020-10-
Kyle Meyer writes:
>> I also have an async implementation for ob-R that's ready after this is
>> merged :)
>
> It's a bit disappointing that only one babel user has tested this out
> and provided feedback, but please feel free to merge this whenever you
> think it's ready.
Strong +1 -- and thank
On 25/04/2021 19:25, Bastien wrote:
Are you still using it? Did anyone tested it?
I realized that I break cache a bit, so the patch should not be applied
in the current form. I have an idea how to fix it but I have found more
problems around (independent of my patch). I did not worried sinc
On Wednesday, 21 April 2021 18:24:27 CEST Nicolas Goaziou wrote:
> In particular, I'm not sure to understand how one system can generate an
> ID based on the heading content and still limit itself to alphanumeric
> characters. For example, what ID are generated with the following
> document?
>
> -
> Uwe Brauer writes:
> With this backtrace alone (which involves org-capture catching the
> internal error), I think it's going to be hard for anyone to guess
> what's going on here. It sounds like once you encounter this error,
> subsequent calls reliably trigger it. Next time y
> Uwe Brauer writes:
> With this backtrace alone (which involves org-capture catching the
> internal error), I think it's going to be hard for anyone to guess
> what's going on here. It sounds like once you encounter this error,
> subsequent calls reliably trigger it. Next time y
Greg Minshall writes:
> Timothy,
>
> interesting. would this show up in #+RESULTS blocks? in (heaven
> forbid!) #+BEGIN_SRC blocks?
>
> cheers, Greg
The screenshot where it shows up is from the following Org buffer
(manually constructed for the example):
#+begin_src julia
[1 2; 3 4]
#+end_s
Dear All,
On Sun, 25 Apr 2021 at 14:50, Bruce D'Arcus wrote:
> How would you deal with these?
>
> #+begin_example
> [cite/-:@doe20; @doe21]
> [cite/-:@doe20; see also @smith19]
> [cite/text:@doe20; see also @smith19]
> #+end_example
>
> My thought is you want to treat the author of the first list
On Sun, Apr 25, 2021 at 3:48 PM András Simonyi wrote:
>
> Dear All,
>
> On Sun, 25 Apr 2021 at 14:50, Bruce D'Arcus wrote:
> > How would you deal with these?
> >
> > #+begin_example
> > [cite/-:@doe20; @doe21]
> > [cite/-:@doe20; see also @smith19]
> > [cite/text:@doe20; see also @smith19]
> > #+
On org-drill, I think someone has already taken it up here a while ago:
https://gitlab.com/phillord/org-drill
On 4/25/21 12:39 AM, Bastien wrote:
Hi Bithov,
we *do* care a lot about backward compatibility*.
We cannot make a strong commitment for contributed libraries and
external ones, though
Hi everyone,
great to see that there's been so much progress since this issue has
last been discussed! Looks really impressive so far.
Two comments/questions:
- I think it should be possible to use some markup in prefixes and suffixes.
- Will this proposal allow multiple bibliographies? I thi
As a new contributor, I wanted to add my two cents. I've submitted a
minor amount of patches (somewhere between 1 and 3, I can't remember
exactly), and I feel that the other problems you raise, primarily the
first one, are obstacles towards that though. Patches like that are
obviously minor, si
Bastien writes:
> Hi Tim,
>
> Tim Cross writes:
>
>> I agree and am willing to help if I can.
>
> Great! Would you agree to be "officially" appointed to this role,
> with Timothy? I put quotes on "officially": when moving toward the
> new maintainance team, I'd like to list maintainers and t
Hi Tim,
thank you very much for your detailed answer.
Tim Cross writes:
> Yes, but with some caveats.
Thank you!
> For these reasons, I'm probably not the best person to assist with the
> review and guidance for patches aimed at adding/extending functionality.
The role of a "contributor ste
Bastien writes:
> Hi Tim,
>
> thank you very much for your detailed answer.
>
> Tim Cross writes:
>
>> Yes, but with some caveats.
>
> Thank you!
>
>> For these reasons, I'm probably not the best person to assist with the
>> review and guidance for patches aimed at adding/extending functional
Hi Ian,
ian martins writes:
> Thanks for fixing this. I re-read the woof documentation and realized
> I needed to put "Applied" at the beginning of the line.
Yes - and also add a "X-Woof-Patch: applied" header in your reply.
Hi Timothy,
Timothy writes:
> +(defun org-plot/redisplay-img-in-buffer (img-file)
> + "Find any overlays for IMG-FILE in the current Org buffer, and refresh
> them."
I guess M-x eldoc RET will choke because the first line of a docstring
should shorter. Other than this nitpick, please feel fr
36 matches
Mail list logo
