Hello,
Marcin Borkowski writes:
> On 2018-10-08, at 09:20, Michael Welle wrote:
[...]
>> Well, on my laptop the initial agenda run takes about 7s or so (150
>> agenda files) using the current day/week agenda ("a"). All subsequent
>> (after loading the files) agenda runs are fast (split second I
Hello,
Marcin Borkowski writes:
> On 2018-10-09, at 13:47, Julius Dittmar wrote:
>
>> Hi Marcin,
>>
>> I can't advise as to profiling to find out what really bogs down agenda
>> building.
>>
>> I found that log messages do bog it down.
>>
>> I have a lot of recurring tasks, which accumulate log
Sebastian Reuße writes:
+ (if (and (string-match "\\`\\(.*\\)/\\([^/]+\\)\\'" answ)
I realize this is overly restrictive if you don’t have
‘org-refile-use-outline-path’ set to ‘file’ and want to refile
under a newly created root headline. AFAICT this would also have
been an issue in
When I create a new headline with =[Alt-Enter]= Under a headline. It looks like
this:
#+begin_src org
,** headline 1
,** headline 2
#+end_src
Then I move point between two asterisks of headline 2. Then I type * again. It
report
following error:
#+begin_example
Debugger entered--Lisp error: (
On Wed, Oct 10, 2018 at 6:05 PM Nicolas Goaziou wrote:
> It is. Fixed. Thank you.
Awesome! Thank you!
Hello,
Kaushal Modi writes:
> I was playing with Org Tangle header-args inheritance and came up with
> this example:
>
> =
>
> #+property: header-args :tangle yes
>
> At Org level 0.
>
> * Heading 1
> :PROPERTIES:
> :header-args: :tangle foo.el
> :END:
> At Org level 1.
>
> #+name: block1
>
Eric S Fraga writes:
> On Wednesday, 10 Oct 2018 at 08:31, Tim Cross wrote:
>
> [...]
[...]
>
>
> And I highly recommend the koma-script classes as opposed to the default
> LaTeX ones. For Sharon, the scrreprt class may be what you want.
Yes, koma-script has been my default as well for some
for cleaning logbook entries, i'd enjoy having an agenda view that
shows every entry that has state changes [above a minimum number of
them to keep it small], with the size of the logbook drawer in the
prefix or so next to the category, sorted by that size.
there would be a corresponding agenda ba
auto-clocking might be interesting.
there would be a concept of a dominating clocking entry similar to
dominating file. i.e. if where you are is not a clocking entry, go up
until you find one that is. if you find none at top level, you create
a clock entry in the logbook there.
if you switch bu
John Hendy writes:
[...]
> So far, Org-ers have been 100% awesome in person, and I look forward
> to running into more down the road. Anyway, just felt like a fun bit
> of news to share, and hopefully you all can nerd out about Org in
> person at some point too!
Somebody tell me if there's a Se
On 2018-10-10, at 18:50, William Denton wrote:
> On 10 October 2018, Marcin Borkowski wrote:
>
>> I am making an Org-mode-based tool to help boost my productivity.
>> ...
>> - is anyone interested in something like this?
>
> I am---I'd love to see what you come up with. I'm doing something
> s
On 2018-10-08, at 17:47, Marco Wahl wrote:
> Hi!
>
>> I found these two commands. They seem to do the same thing. What is
>> the difference?
>
> This is an example illustrating the difference.
>
> - Have point on the *table* of the following subtree.
>
>
> --8<---cut here-
On 2018-10-08, at 17:58, Eric S Fraga wrote:
> On Monday, 8 Oct 2018 at 17:26, Marcin Borkowski wrote:
>> Hi all,
>>
>> I found these two commands. They seem to do the same thing. What is
>> the difference?
>
> These will only do the same thing if your element (where point is) happens to
>
On 2018-10-08, at 09:20, Michael Welle wrote:
> Hello,
>
> Marcin Borkowski writes:
>
>> Hi Orgers,
>>
>> my agenda takes almost 10 seconds to show up. Are there any ideas for
>> profiling that?
>>
>> I suspect that archiving a lot of old entries I don't use anymore might
>> help, but is ther
On 2018-10-09, at 13:47, Julius Dittmar wrote:
> Hi Marcin,
>
> I can't advise as to profiling to find out what really bogs down agenda
> building.
>
> I found that log messages do bog it down.
>
> I have a lot of recurring tasks, which accumulate log entries for every
> closing (which in fact
On 2018-10-09, at 18:11, Nicolas Goaziou wrote:
> Hello,
>
> Adam Porter writes:
>
>> My feedback is: there be dragons. ;) The Agenda code is very
>> complicated and hard to follow, and it's hard to optimize something that
>> is hard to understand.
>
> And hard to maintain. We should really
On 2018-10-09, at 08:37, Adam Porter wrote:
> Hi Marcin,
>
> [...]
>
> If you haven't seen them already, you may find my org-ql and
> org-ql-agenda code useful. org-ql-agenda presents an Agenda-like
> buffer. N.B. It does *not* implement most of the Agenda features, but
> it does emulate an O
Thanks for making it happen John! I had a great visit, and hope to see some
org-mode adoption in a company environment. That would be amazing!
John
---
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburg
On 10 October 2018, Marcin Borkowski wrote:
I am making an Org-mode-based tool to help boost my productivity.
...
- is anyone interested in something like this?
I am---I'd love to see what you come up with. I'm doing something similar, but
much less fancy, with clock tables and some R:
htt
Hi Orgers,
I am making an Org-mode-based tool to help boost my productivity.
I am constantly fighting a losing battle with distractions. I figured
out that showing me how much time I spent goofing around would help me
stay on track (being a math geek and a gamer, my "let's break my
yesterday's s
On Wednesday, 10 Oct 2018 at 08:31, Tim Cross wrote:
[...]
> One of the most common mistakes I see when people start using latex as
> the basis for document generation is ad hoc tweaking of the
> style. This is an unfortunate consequence of most of us being exposed
> to traditional word processor
Hello Nicolas,
Nicolas Goaziou writes:
Compiling your patch generates the following warnings.
org.el:11417:1:Warning: Unused lexical variable ‘parent’
org.el:11417:1:Warning: Unused lexical variable ‘child’
org.el:11417:1:Warning: Unused lexical variable
‘parent-target’
Goo
* org.el (org--refile-new-path): Add.
(org-refile): Use it.
(org-refile-new-child): Make new nodes more compact.
* test-org.el (test-org/org-refile): Add test.
While ‘org-refile’ currently supports creating new headlines when
refiling, only one single headline can be created this way. For
conveni
Hello,
Sebastian Reuße writes:
> * org.el (org--refile-new-path): Add.
> (org-refile): Use it.
> (org-refile-new-child): Make new nodes more compact.
>
> * test-org.el (test-org/org-refile): Add test.
>
> While ‘org-refile’ currently supports creating new headlines when
> refiling, only one sing
24 matches
Mail list logo
