From: Carsten Dominik <carsten.dominik@gmail.com>
To: Bernt Hansen <bernt@norang.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: Font problem with copying subtrees
Date: Mon, 4 May 2009 17:01:41 +0200 [thread overview]
Message-ID: <A05993D0-F1D3-4B3E-BB76-D348E80701A3@gmail.com> (raw)
In-Reply-To: <87fxfyt5fq.fsf@gollum.intra.norang.ca>
Very strange, so far I cannot reproduce this.
- Carsten
On Apr 24, 2009, at 5:52 PM, Bernt Hansen wrote:
> Hi Carsten!
>
> I got a chance to try out the new C-c C-x c
> (org-clone-subtree-with-time-shift) yesterday while doing my quarterly
> accounting (ugh) and this is much better than the old way I dealt with
> these repeating tasks. Thanks!!
>
> I noticed a problem with font locking (if that's what you call it)
> when
> copying subtrees and supplying a date.
>
> I started with the following file:
>
> ,----[ x.org ]
> |
> | * Level One
> | ** TODO One
> | *** TODO One.One
> | *** TODO One.Two
> | ** TODO Two
> | ** TODO Three
> | *** TODO Three.One
> | ** TODO Four
> | * TODO Next thing
> `----
>
> and with the cursor on "* Level One" I did
> C-c C-x c
> Number of clones to produce: 1 RET
> Date shift per clone (e.g. +1w, empty to copy unchanged): +1y
>
> and the copied clone was all black text.
>
> Of course I just undid it now and redid it and it looks correct :/
>
> I noticed this when copying my large-ish subtrees for the accounting
> quarterly work because tables were not blue, no heading levels were
> coloured etc.
>
> Let me know if you need more information.
>
> -Bernt
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2009-05-04 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 15:52 Font problem with copying subtrees Bernt Hansen
2009-05-04 15:01 ` Carsten Dominik [this message]
2009-05-04 17:07 ` Bernt Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A05993D0-F1D3-4B3E-BB76-D348E80701A3@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).