Nicolas Goaziou writes:
> Hello,
>
> Julien Cubizolles writes:
>
>> Did I miss an important change to the way org-agenda-files is to be
>> used ?
>
> It is probably related to the change in `org-agenda-time-grid'. See new
> docstring.
I've looked into it but the example I provided is run from e
Thanks for your comments, John, that is very interesting. I'll have to
check out your db code.
I'll drop a penny in the bucket with this:
http://github.com/alphapapa/org-agenda-ng
I spent a few hours trying an alternative approach that uses
org-element-parse-buffer to parse each file, then oper
Hi!
I discovered a bug in the ox-md exporter and have created a patch to fix it:
Previously, this image link:
[[https://git-scm.com/images/l...@2x.png]]
would export to:
![img](//git-scm.com/images/l...@2x.png)
which is an invalid markdown image, and won't display properly in
browsers and other
I think the only viable first step is the profiling.
One of the main reasons I like org-mode is that all the data is just
text in files and it does not have any dependencies on other external
systems apart for publishing/exporting.
While there may be a need for external utilities to improve perf
Hello,
Christian Garbs writes:
> Byte-compiling works and gave me 5 warnings about unused variables and
> arguments which I could fix in different ways.
Note that the usual solution to get rid of unused arguments is to prefix
their name with "_".
> Currently I run into a problem with the test
Hello,
Michaël Cadilhac writes:
> Hi there everyone;
>
> Here's the ECM.
>
> init.el:
> (require 'org)
> (setq org-refile-use-outline-path (quote file))
>
> Now open an Org file, say foo.org, and type C-u C-c C-w foo.org/ RET
> At org.el:11832, pos is nil.
Fixed. Thank you.
Regards,
--
Nicol
Hello,
Michaël Cadilhac writes:
> Subject: [PATCH] org-capture.el: Document what the time stamp is in capture
> templates
>
> * lisp/org-capture.el (org-capture-templates): Make explicit that the time
> stamp aware %-escapes are influenced by `org-capture-use-agenda-date'.
Applied. Thank you.
Hello,
Adam Porter writes:
> My only feedback here is that maybe the startup keywords would be more
> descriptive if they were something like "table-shrink" or
> "column-shrink". I could imagine some new Org users conflating "folded"
> and "shrink" until they have used a more advanced feature l
Thanks a lot for this piece of work! Very useful (at least to me).
Fabrice
2017-08-05 23:35 GMT+02:00 John Kitchin :
> Hi everyone,
>
> I moved my ipynb exporter to a new repo at https://github.com/
> jkitchin/ox-ipynb. I am planning to submit it to MELPA in the next week
> or two. If anyone is
Hello,
Eric S Fraga writes:
> Thanks Nicolas. Sounds very nice, matching at least my use cases quite
> well. I'll give this a try soon and will get back to you.
For the record, I updated the "hide-table-column" branch again.
`org-table-toggle-column-width' is now bound to "C-c TAB". I remove
Hello,
Karl Voit writes:
> My daily agenda takes twenty seconds, my weekly approximately a
> minute and generating a monthly agenda is something I can only do
> when I plan to leave the computer for a longer break.
>
> Org-mode does not scale well, I'm afraid.
>
> Repeatedly going through all ag
Hello,
John Kitchin writes:
> I can think of two possibilities for a future approach (besides a deep dive
> on profiling the current elisp to improve the speed there). They both
> involve some substantial coding though, and would probably add
> dependencies. I am curious what anyone things about
Hello,
Julien Cubizolles writes:
> Did I miss an important change to the way org-agenda-files is to be
> used ?
It is probably related to the change in `org-agenda-time-grid'. See new
docstring.
Regards,
--
Nicolas Goaziou
I can think of two possibilities for a future approach (besides a deep dive
on profiling the current elisp to improve the speed there). They both
involve some substantial coding though, and would probably add
dependencies. I am curious what anyone things about these, or if there are
other ideas.
O
Hi everyone,
I moved my ipynb exporter to a new repo at
https://github.com/jkitchin/ox-ipynb. I am planning to submit it to MELPA
in the next week or two. If anyone is interested in checking it out, it
would be helpful to spot issues prior to MELPA release!
The TL;DR version is this adds an org e
I noticed today (I hadn't used it in a long time) that the today and/or
time-grid view in the agenda seems broken.
With emacs -Q running Org mode version 9.0.9 (release_9.0.9 @
/usr/share/emacs/26.0.50/lisp/org/)
(setq org-agenda-files '("~/tmp/test-org/todo.org"))
todo.org
--8<---c
* Adam Porter wrote:
> Thierry Banel writes:
>
>> Alternatively you have the orgtbl-aggregate package available on Melpa.
>>
>> #+BEGIN: aggregate :table "myvalues" :cols "min(Values) max(Values)
>> mean(Values)"
>>
>> | min(Values) | max(Values) | mean(Values) |
>> |-+-+-
Hi Adam,
Ah, didn't spot that! Thanks for the hint.
Cheers, Simon
On 5/08/2017 10:51 PM, "Adam Porter" wrote:
> Simon Guest writes:
>
> > I am a user of ox-taskjuggler. Since I am currently running the
> > version of org mode bundled with Emacs, this doesn't include the
> > contrib stuff like
Thanks for the insight!
* Adam Porter wrote:
>
> But doing that would, as Carsten said, require rewriting a lot of code.
> Essentially you'd be creating a new agenda system, so you'd have to
> reimplement a lot of existing code. You could do it in parallel, rather
> than replacing existing code,
Hi!
On Thu, Aug 03, 2017 at 12:49:44PM +0200, Nicolas Goaziou wrote:
> Christian Garbs writes:
> > Regarding the lexical-binding: How can I check if byte-compiling is
> > successful?
>
> M-x emacs-lisp-byte-compile
Byte-compiling works and gave me 5 warnings about unused variables and
argumen
Nicolas Goaziou writes:
> Hello,
>
> Eric Abrahamsen writes:
>
>> For example, the below looks like something you'd find in an Emacs
>> manual.
>>
>> #+BEGIN_SRC texinfo
>> @table @kbd
>> @item C-x C-f
>> @kindex C-x C-f
>> @findex find-file
>> Visit a file (@code{find-file}).
>> @it
Hello,
Josh Moller-Mara writes:
> Recently I've found that clocking in to a repeating task is giving me an
> incorrect "task time since last repeat". Normally, when I clock into a task,
> mark it as done, and clock in again, I expect the starting clock time to
> be 0. In this example:
>
> * TODO
On 5 August 2017 at 12:46, Adam Porter wrote:
> If you could send a TINYCHANGE patch to the docstring, I'm sure Nicolas
> would be grateful! :)
Sure thing!
M.
From 7c8569f6bf694bb45ac5334c3bcb13e54e0d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Micha=C3=ABl=20Cadilhac?=
Date: Sat, 5 Aug 2017
Simon Guest writes:
> I am a user of ox-taskjuggler. Since I am currently running the
> version of org mode bundled with Emacs, this doesn't include the
> contrib stuff like ox-taskjuggler. So currently I have had to grab a
> copy of ox-taskjuggler.el manually, and stick it on my load path,
> man
Michaël Cadilhac writes:
> Thanks for your expertise Adam.
Glad I could help, but I think you did the sleuthing here. ;)
> It seems indeed that org-agenda-capture (or equivalently, setting
> org-capture-use-agenda-date) affects the default date at all stages,
> i.e., for %u and for the defau
On 5 August 2017 at 04:27, Adam Porter wrote:
> Michaël Cadilhac writes:
>
>> However, suppose I'm in Calfw; I jump to some date, hit SPACE and I'm
>> now in Org-Agenda mode, ready to hit k to capture (because Calfw-Org
>> does not offer this directly). Now I expect %U to still be the
>> current
Hello,
Allen Li writes:
> * lisp/org.el (org-tag-alist, org-tag-persistent-alist):
> Add non-keyed tag type.
Thank you. For some reason, I'm not able to apply your patch on "maint"
branch. Could you rebase it on top of that branch and send it again?
Regards,
--
Nicolas Goaziou
Hello,
Nicolae Cindea writes:
> I think there is a bug in org-2017073: when I store the agenda-view in
> .ics format, all the entries which span on multiple days are
> duplicated -- for each day there is a new event in the .ics file.
Fixed. Thank you.
Regards,
--
Nicolas Goaziou
Hello,
Eric Abrahamsen writes:
> For example, the below looks like something you'd find in an Emacs
> manual.
>
> #+BEGIN_SRC texinfo
> @table @kbd
> @item C-x C-f
> @kindex C-x C-f
> @findex find-file
> Visit a file (@code{find-file}).
> @item C-x C-r
> @kindex C-x C-r
> @findex
Hi
I like orgtbl-mode and orgtbl-insert-table-or-matrix in latex files a
lot, since they simplify considerably the construction of tables and
matrixes.
I am looking for a similar functionality for src-code-blocks.
The idea is to insert, surrounded by a comment environment,
src-code-blocks, to e
Dear Org People,
I am a user of ox-taskjuggler. Since I am currently running the version of
org mode bundled with Emacs, this doesn't include the contrib stuff like
ox-taskjuggler. So currently I have had to grab a copy of ox-taskjuggler.el
manually, and stick it on my load path, manually.
Since
Hello,
I think there is a bug in org-2017073: when I store the agenda-view in .ics
format, all the entries which span on multiple days are duplicated -- for each
day there is a new event in the .ics file.
Thanks,
Nicolae.
Hey there,
Recently I've found that clocking in to a repeating task is giving me an
incorrect "task time since last repeat". Normally, when I clock into a task,
mark it as done, and clock in again, I expect the starting clock time to
be 0. In this example:
* TODO Stuff
SCHEDULED: <2017-08-04 F
33 matches
Mail list logo