From: Antoine Levitt <antoine.levitt@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: UPDATE schedule/deadline and ido-mode conflict
Date: Tue, 12 Oct 2010 10:57:48 +0200 [thread overview]
Message-ID: <878w23u6sz.fsf@gmail.com> (raw)
In-Reply-To: 83F12E1F-C203-4BC3-860B-41B1E5573647@gmail.com
14/05/10 13:33, Carsten Dominik
> On May 14, 2010, at 10:27 AM, David Lee wrote:
>
>> On 05/13/2010 11:04 AM, David Lee wrote:
>>> On 05/13/2010 10:26 AM, Nick Dokos wrote:
>>>> David Lee<zhushenli2@gmail.com> wrote:
>>>>
>>>>> On 05/12/2010 11:46 PM, Nick Dokos wrote:
>>>>>> David Lee<zhushenli2@gmail.com> wrote:
>>>>>>
>>>>>>
>>>>>>> After insert schedule and deadline by C-c C-s, C-c C-d, I switch
>>>>>>> buffer by ido-mode command ido-switch-buffer.
>>>>>>>
>>>>>>> Emacs will give out a message:
>>>>>>> Error in post-command-hook: (void-variable org-ans1)
>>>>>>>
>>>>>>> And ido-switch-buffer doesn't work.
>>>>>>>
>>>>>>> My environment: Emacs 23.1, Org-mode 6.36.
>>>>>>>
>>>>>>
>>>>>> Please post a backtrace. To find out how to get a backtrace, read
>>>>>> section 1.4, "Feedback", of the Org manual.
>>>>>>
>>>>>
>>>>> I turn on "Enter Debugger On error" all the time, and follow the
>>>>> instruction in Org Info.
>>>>> But I cannot get the backtrace, seems its not an *error* (didn't
>>>>> fire
>>>>> up elisp debugger), but just a message?
>>>>>
>>>>> The conflict make me give up schedule/deadline.
>>>>>
>>>>> So, any other suggestion on get the backtrace?
>>>>>
>>>>
>>>> Nope - no ideas/suggestions: seems to me it should have triggered.
>>>>
>>>> What's the value of post-command-hook just before you get the error?
>>>> Note that that's a buffer-local variable, so you'll have to
>>>> evaluate it
>>>> (using `C-h v post-command-hook<RET>') in the correct buffer.
>>>>
>>>> Nick
>>>>
>>>>
>>>
>>> Hi, Nick, the error is not consistent, and I cannot always capture
>>> it.
>>> Is it related to the variable org-ans1?
>>>
>>> From my local buffer (I am *not* very sure whether the value is
>>> before
>>> the error, since sometimes C-h v affect the error conditions and make
>>> ido-switch-buffer work, I will try to investigate the error when I
>>> can
>>> reproduce it):
>>>
>>> ;;;
>>> post-command-hook is a variable defined in `C source code'.
>>> Its value is
>>> (linum-update-current t flyspell-post-command-hook)
>>>
>>> Local in buffer emacs.org; global value is
>>> (global-font-lock-mode-check-buffers
>>> global-auto-composition-mode-check-buffers
>>> global-linum-mode-check-buffers cua--post-command-handler)
>>>
>>>
>>> - David
>>
>> I tried DEADLINE today. The steps are:
>> 1. C-c C-d to add DEADLINE, choose date from calendar.
>
> How exactly do you choose it? Keyboard,mouse? List the exact key/
> envents, please
>
> - Carsten
>
Hi,
I get the same bug when selecting a date by mouse. It seems that
org-read-date-display is added to post-command-hook and never
deleted. The code responsible for this seems to be:
(unwind-protect
(progn
(use-local-map map)
(add-hook 'post-command-hook 'org-read-date-display)
(setq org-ans0 (read-string prompt default-input
'org-read-date-history nil))
;; org-ans0: from prompt
;; org-ans1: from mouse click
;; org-ans2: from calendar motion
(setq ans (concat org-ans0 " " (or org-ans1 org-ans2))))
(remove-hook 'post-command-hook 'org-read-date-display)
After the bug happens, every command causes the error (void-variable
org-ans1). post-command-hook looks like:
post-command-hook is a variable defined in `C source code'.
Its value is nil
Local in buffer *followup to Carsten Dominik on gmane.emacs.orgmode*;
global value is
(global-font-lock-mode-check-buffers
global-highlight-parentheses-mode-check-buffers
autopair-global-mode-check-buffers org-read-date-display)
(it is locally set to nil by emacs after an error is triggered, see the
help page of post-command-hook)
>>
>> 2. Try ido-switch-buffer, didn't work and Emacs show
>> Error in post-command-hook: (void-variable org-ans1)
>>
>> 3. C-h v post-command-hook, Emacs show
>> post-command-hook\ \ \ is void as a variable.
>>
>> 4. Try ido-switch-buffer, it worked.
>>
>> So, I use *C-h v post-command-hook* to solve the problem :)
>>
>> Emacs 23.1 on Ubuntu9.04, Org-mode 6.36.
>>
>>
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Please use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
> - Carsten
>
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
prev parent reply other threads:[~2010-10-12 9:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 15:40 schedule/deadline and ido-mode conflict David Lee
2010-05-12 15:46 ` Nick Dokos
2010-05-13 1:49 ` David Lee
2010-05-13 2:26 ` Nick Dokos
2010-05-13 3:04 ` David Lee
2010-05-14 8:27 ` UPDATE " David Lee
2010-05-14 11:33 ` Carsten Dominik
2010-10-12 8:57 ` Antoine Levitt [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=878w23u6sz.fsf@gmail.com \
--to=antoine.levitt@gmail.com \
--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).