emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "G. Martin Butz" <mb@mkblog.org>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Strange Behaviour while rescheduling date
Date: Sat, 21 Sep 2013 19:38:36 +0200	[thread overview]
Message-ID: <523DD99C.9000900@mkblog.org> (raw)
In-Reply-To: <523C9E31.7090107@mkblog.org>

Hi,

once more me - in case anyone is interested. I finally went through my 
config file step by step. The responsible lines in my .emacs were:

---------------------------8<------------------------------------
(defadvice split-window (after move-point-to-new-window activate)
   "Moves the point to the newly created window after splitting."
   (other-window 1))
---------------------------8<------------------------------------

Martin

Am 20.09.2013 21:12, schrieb G. Martin Butz:
> Hi,
>
> I tried to describe this error a while ago, but did not get any response
> - probably due to the fact, that I can not find out, how to securely
> reproduce this very annoying behaviour; I will try to describe:
>
> 1. I try to reschedule an entry (C-c C-s)
> 2. The buffer with the org file seems to be replaced by a calendar
> 3. Futhermore 2 additional buffers appear with the calendar in it
> 4. If can not assign a date meaning cursor movement (Shift Left/Right)
> seems to be random e.g. skipping a few day and also going in the wrong
> direction (e.g. left means right)
> 5. If I try quitting emacs, I am asked if I want to save the original
> org-mode buffer (in which I tried to reschedule a date)
> 6. If I dare to do this, emacs will write the calender into this buffer
> thereby erasing the original org mode file.
>
> I tried to deliver a backtrace (load org-mode and activate the debugger
> according to [1]) but: There is no error message at all (!sic)!
>
> The only thing I could do is to make a screenshot showing state no. 3 [2].
>
> This makes keeping track of dates in org-mode almost unusable for me.
> Does anyone have an idea, what I could do to pinpoint this behaviour?
>
> I am running org-mode 8.2 (updated today, but have had this error since
> a while) on emacs 24.3.1 on Linux Crunchbang Waldorf.
>
> Thanks for any hints and thanks alot for wonderful org-mode in general
> Martin
>
> [1] <http://orgmode.org/manual/Feedback.html>
> [2] <http://www.mkblog.org/download/emacs-org-mode-calendar.png>


-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| G. Martin Butz, mb@mkblog.org, 0421 98749324, www.mkblog.org |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

      parent reply	other threads:[~2013-09-21 17:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-20 19:12 Strange Behaviour while rescheduling date G. Martin Butz
2013-09-21 16:41 ` G. Martin Butz
2013-09-23  7:46   ` Sebastien Vauban
2013-09-23  7:50     ` Carsten Dominik
2013-09-23  8:34     ` G. Martin Butz
2013-09-21 17:38 ` G. Martin Butz [this message]

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=523DD99C.9000900@mkblog.org \
    --to=mb@mkblog.org \
    --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).