On Wed, May 20, 2020 at 10:12:38PM -0500, James R Miller wrote:
> > I think issue tracking could happen on a mailing list. If you tag an
> > issue's subject line with OPEN: or CLOSE:, a bot could mail a summary of
> > the OPEN: issues to the list periodically (in theory).
>
> Something like that
Greg Minshall writes:
> hi. i'm running R code from an org mode file. i was having a problem
> where a code block that *was* returning a value result was not returning
> the results into the buffer.
>
> (after long head-scratching) this appears to be because my code was
> returning more lines
> I think issue tracking could happen on a mailing list. If you tag an
> issue's subject line with OPEN: or CLOSE:, a bot could mail a summary of
> the OPEN: issues to the list periodically (in theory).
Something like that would be nice; the bot could even store such info in an org
file that
George Sokolsky writes:
> Kyle, could you please apply the patch to the org repository?
Applied (5e2490bdf).
On 5/18/20 5:24 PM, Anthony Carrico wrote:
Does org-mode have an issue tracker, to keep track of which issues are
active, or is it just this mailing list?
I'm the OP here. My first post to this list generated a lot of feedback.
I'm not sure I have an opinion, it was an honest question, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nicolas Goaziou writes:
> Hello,
>
> stardiviner writes:
>
>> I found org link can't get link description easily.
>>
>> I googled it how to get link description. Found this solution. But it's not
>> intuitive.
>>
>> #+begin_src emacs-lisp
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
John Kitchin writes:
> On Tue, May 19, 2020 at 6:51 PM stardiviner wrote:
>
>> I actually borrowed code from your code example, Because I want to do the
>> following:
>>
>
> Where did you find code that uses org-element-property on a link like
Aloha everyone,
Sometimes a "lower tech" solution is best, or at least offers
a lot of advantages.
What I see as the advantages of resolving issues through a
mailing list are:
* Minimal barriers to entry. If you have an email client of
ANY type, you're in. No need for anything more. I think
Hello,
I'd like to set org-todo-keywords and org-todo-keyword-faces through
directory-local variables, to get rid of duplicate #+SEQ_TODO lines in
my Org files[1].
Right now I see two obstacles for this to work:
(1) org-set-regexps-and-options, which sets up a bunch of TODO-related
Ivan Sokolov writes:
> I ran into problems with ob-js. When resolving them, I found that require
> ('sys') is deprecated, there is a patch.
>
> diff --git a/lisp/ob-js.el b/lisp/ob-js.el
> index 7592040ab..d459e8069 100644
> --- a/lisp/ob-js.el
> +++ b/lisp/ob-js.el
> @@ -65,7 +65,7 @@
>
Hello,
"Dauer, Michael" writes:
> This was different in earlier versions.
I couldn't find an earlier version where that was the case. This
doesn't mean there is none, of course.
> And what about date and time. Are these macros also expected to be defined
> manually before?
I cannot
Hello everyone,
I have been following the org-mode ML and I have seen the discussion about
having a bug tracker. I wanted to offer my 2 cents as a non-developer; barely a
power user. Org-mode works incredibly well and I use it on a daily basis. It is
true that development is very active.
I second that.
Nicolas, thank you!
Great product, better vision, high energy!
‐‐‐ Original Message ‐‐‐
On Wednesday, May 20, 2020 7:12 AM, Stefan Nobis wrote:
> Detlef Steuer ste...@hsu-hh.de writes:
>
> > I would go as far as saying this list is one of the fastest
> > reacting
On Tue, May 19, 2020 at 6:51 PM stardiviner wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
>
> John Kitchin writes:
>
> > The face function only takes the link path, which is a string. you cannot
> > use org-element-property on it.
> >
> > Maybe you want something like this:
> >
>
On Tue, May 19, 2020 at 8:38 PM Kyle Meyer wrote:
> Nicolas Goaziou writes:
>
> > At first glance, it looks harmless. If the test suite passes, we can
> > apply it.
>
> The test suite does pass with the change. Pushed, along with a
> regression test (962b8e765).
>
Thank you for the debug and
Hello,
stardiviner writes:
> I found org link can't get link description easily.
>
> I googled it how to get link description. Found this solution. But it's not
> intuitive.
>
> #+begin_src emacs-lisp
> (defun get-description-at-point ()
> (interactive)
> (let ((link
Detlef Steuer writes:
> I would go as far as saying *this list* is one of the fastest
> reacting amd friendliest communities I have been part of. The job
> Nicolas does is just awesome.
+1!
--
Until the next mail...,
Stefan.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I found org link can't get link description easily.
I googled it how to get link description. Found this solution. But it's not
intuitive.
#+begin_src emacs-lisp
(defun get-description-at-point ()
(interactive)
(let ((link
Am Wed, 20 May 2020 10:22:56 +0100
schrieb Eric S Fraga :
> On Tuesday, 19 May 2020 at 18:57, Russell Adams wrote:
> > My personal opinion is I'd always prefer to use my mail client over
> > some website.
>
> +∞!
How to add more now? Same here. Mail is functionally superior to a lot
of
On Tuesday, 19 May 2020 at 18:57, Russell Adams wrote:
> My personal opinion is I'd always prefer to use my mail client over some
> website.
+∞!
There are some communities that I would love to participate in but do
not because they use, for instance, discourse which has a horrible email
This was different in earlier versions.
And what about date and time. Are these macros also expected to be defined
manually before?
Nicolas Goaziou schrieb am Mi., 20. Mai 2020,
00:53:
> Hello,
>
> "Dauer, Michael" writes:
>
> > mist.org>>>
> >
> > * test
> > foo {{{author}}} bar
Hi Kyle,
thanks a lot for your workaround! I just tested it and it almost does what I am
looking for.
The only thing that does not work is to give a range of time, i.e. 10:00-12:00.
And looking at your code it is clear, that this cannot work because neither
"%t" nor "%T" can do this.
I
22 matches
Mail list logo
