emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Karl Voit <devnull@Karl-Voit.at>
To: emacs-orgmode@gnu.org
Subject: Re: [Bug] Removing scheduled/deadline shows "Entry repeats:..." which is not true
Date: Sat, 26 Oct 2013 10:32:17 +0200	[thread overview]
Message-ID: <2013-10-26T10-30-26@devnull.Karl-Voit.at> (raw)
In-Reply-To: 20131026004129.6efa5451@aga-netbook

* Marcin Borkowski <mbork@wmi.amu.edu.pl> wrote:
> Dnia 2013-04-18, o godz. 10:53:30
> Karl Voit <devnull@Karl-Voit.at> napisał(a):
>
>> * Bastien <bzg@gnu.org> wrote:
>> > Hi Karl,
>> >
>> > Karl Voit <devnull@Karl-Voit.at> writes:
>> >
>> >> Sorry for the late reply. This is because I do have troubles to
>> >> come up with a minimal example. Starting Emacs with debug-init
>> >> does not show this issue. I guess I have to strip down my config
>> >> until this behavior changes (or add el-configs step by step). I'll
>> >> report.
>> >
>> > Thanks.  The bug looks pretty bad, so I hope this is just a problem
>> > in your configuration.  But still, I hope this is not a problem in
>> > the way Org allows you to combine several options.
>> 
>> I'm a bit puzzled since this issue seem to have disappeared.
>> Yesterday, I was facing this message but today (without upgrading
>> Org-mode!) I can not reproduce it either :-O
>> 
>> Let's say it was something deeply related to my config which changed
>> meanwhile.
>
> Just a few seconds ago I experienced something similar (I was changing
> the TODO state, and there was *no* SCHEDULED keyword anywhere (!) in
> the file).  I diffed the only buffer that changed (the current one) to
> the saved version, and found nothing suspicious. It's too late for me to
> analyse this (it's 00:40 here;)), but if the problem persists, I'll
> try to report (if I'm able to prepare an ECM).

From time to time I recognize this strange issue. However, since
there were no reports of other people, I thought that this is some
issue related to my own set-up[1] and ignored it.

So: at my side, it appears from time to time and I still do not have
that much Emacs knowledge to debug it.

  1. https://github.com/novoid/dot-emacs
-- 
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
       > get Memacs from https://github.com/novoid/Memacs <

https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github

  reply	other threads:[~2013-10-26  8:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08 12:17 [Bug] Removing scheduled/deadline shows "Entry repeats:..." which is not true Karl Voit
2013-04-08 20:01 ` Bastien
2013-04-17 11:58   ` Karl Voit
2013-04-18  8:08     ` Bastien
2013-04-18  8:53       ` Karl Voit
2013-10-25 22:41         ` Marcin Borkowski
2013-10-26  8:32           ` Karl Voit [this message]
2013-11-06  9:00           ` Bastien

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=2013-10-26T10-30-26@devnull.Karl-Voit.at \
    --to=devnull@karl-voit.at \
    --cc=emacs-orgmode@gnu.org \
    --cc=news1142@Karl-Voit.at \
    /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).