Hello,
Kyle Meyer writes:
> Yes, c31462f33 resolved the issue. That commit also introduced a
> regression: a blank string passed as the SHIFT argument causes an error.
> I've followed up with 1fbc7a424 to restore the previous behavior.
Indeed. Thank you.
Regards,
--
Nicolas Goaziou writes:
> Karl Voit writes:
[...]
>> You're right, I can confirm your issue. I get "Before first headline
>> at position 1 in buffer *temp*" as well.
>
> Fixed (hopefully) this time.
Yes, c31462f33 resolved the issue. That
Hello,
Karl Voit writes:
> * Kyle Meyer wrote:
>>
>> Thanks. The additional check looks good, as it replaces an error with a
>> more appropriate user-error and gives an error message that is a bit
>> more specific.
>>
>> However, the re-positioning of
* Kyle Meyer wrote:
>
> Thanks. The additional check looks good, as it replaces an error with a
> more appropriate user-error and gives an error message that is a bit
> more specific.
>
> However, the re-positioning of the org-back-to-heading call seems
> problematic because the
Nicolas Goaziou writes:
> Thank you. I applied your patch with an additional check.
Thanks. The additional check looks good, as it replaces an error with a
more appropriate user-error and gives an error message that is a bit
more specific.
However, the re-positioning
Hello,
* Nicolas Goaziou wrote:
>
> Kyle Meyer writes:
>
>> Subject: [PATCH] org-clone-subtree-with-time-shift: Fix timestamp search
>
> Thank you. I applied your patch with an additional check.
I pulled the fix from "maint" and I re-tested my test
Hello,
Kyle Meyer writes:
> Subject: [PATCH] org-clone-subtree-with-time-shift: Fix timestamp search
>
> * lisp/org.el (org-clone-subtree-with-time-shift): Move to the
> beginning of the heading before the timestamp search so that the
> user will be prompted for a time
Karl Voit writes:
> Hi!
>
> I wrote a blog article on how I am using Org with recurring events
> or tasks:
> http://karl-voit.at/2017/01/15/org-clone-subtree-with-time-shift/
>
> As Michael Maurer stated in a comment below,
> org-clone-subtree-with-time-shift does not ask
* Karl Voit wrote:
>
> As Michael Maurer stated in a comment below,
> org-clone-subtree-with-time-shift does not ask for time-shift
> depending on the location of the cursor.
He is using Org-mode version 8.2.10.
--
get
Hi!
I wrote a blog article on how I am using Org with recurring events
or tasks:
http://karl-voit.at/2017/01/15/org-clone-subtree-with-time-shift/
As Michael Maurer stated in a comment below,
org-clone-subtree-with-time-shift does not ask for time-shift
depending on the location of the cursor.
Hi David,
David Rogers davidandrewrog...@gmail.com writes:
Is this something where the default has been changed recently?
This behavior is new in 8.0-pre -- when in doubts, check the next
release notes:
http://orgmode.org/Changes.html
I'm still in the process of completing these notes for
Hi everyone
I like to use org-clone-subtree-with-time-shift (C-c C-x c) fairly
frequently in some of my Org-mode files. Lately, it seems to have
changed its function so that it creates only an exact clone, and doesn't
prompt me for the time shift. Can other people reproduce this on a
fairly
Hi David,
David Rogers davidandrewrog...@gmail.com writes:
I like to use org-clone-subtree-with-time-shift (C-c C-x c) fairly
frequently in some of my Org-mode files. Lately, it seems to have
changed its function so that it creates only an exact clone, and doesn't
prompt me for the time
Bastien b...@gnu.org writes:
Hi David,
David Rogers davidandrewrog...@gmail.com writes:
I like to use org-clone-subtree-with-time-shift (C-c C-x c) fairly
frequently in some of my Org-mode files. Lately, it seems to have
changed its function so that it creates only an exact clone, and
Hallo all,
when I do a org-clone-subtree-with-time-shift command, it adds up a
left over line with just :ID: in it.
The most simple way to produce it is with cloning just a single TODO
item like this on:
..
TODO Trockenstellen
SCHEDULED:
* Bernt Hansen be...@norang.ca wrote:
Karl Voit devn...@karl-voit.at writes:
When an entry got processed by org-clone-subtree-with-time-shift,
its :CREATED: property gets shifted too:
#+begin_example
* 2011-10-04 Tue test
SCHEDULED: 2011-10-05 Wed
:PROPERTIES:
:CREATED: 2011-10-04 Tue
Karl Voit devn...@karl-voit.at writes:
Hi!
When an entry got processed by org-clone-subtree-with-time-shift,
its :CREATED: property gets shifted too:
#+begin_example
* 2011-10-04 Tue test
SCHEDULED: 2011-10-05 Wed
:PROPERTIES:
:CREATED: 2011-10-04 Tue 17:27
:END:
* 2011-10-11 Tue test
Hi!
When an entry got processed by org-clone-subtree-with-time-shift,
its :CREATED: property gets shifted too:
#+begin_example
* 2011-10-04 Tue test
SCHEDULED: 2011-10-05 Wed
:PROPERTIES:
:CREATED: 2011-10-04 Tue 17:27
:END:
* 2011-10-11 Tue test
SCHEDULED: 2011-10-12 Wed
:PROPERTIES:
:CREATED:
18 matches
Mail list logo