emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: Weirdness with Agenda and "C-u r"
Date: Sun, 17 Jan 2016 14:03:11 +0800	[thread overview]
Message-ID: <87ziw4wxnk.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 84wpr9amul.fsf@gmail.com

Marco Wahl <marcowahlsoft@gmail.com> writes:

> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Something seems to have gone off with the `org-tags-view' Agenda view:
>> if I hit "C-u r" to search with another string, I get this traceback:
>>
>> Debugger entered--Lisp error: (invalid-function 4)
>>   (4)
>>   (org-tags-view (4) (if current-prefix-arg nil "publishing"))
>>   (let nil (org-tags-view (4) (if current-prefix-arg nil "publishing")))
>>   eval((let nil (org-tags-view (4) (if current-prefix-arg nil "publishing"))))
>>   org-let(nil (org-tags-view (4) (if current-prefix-arg nil "publishing")))
>>   org-agenda-redo((4))
>>   funcall-interactively(org-agenda-redo (4))
>>   call-interactively(org-agenda-redo nil nil)
>>   command-execute(org-agenda-redo)
>>
>> I tried e-debugging `org-agenda-redo', but something magic happens when
>> it gets to the org-let, and no light was shed.
>
>> I seem to remember there have been some changes to the tag matching code
>> recently -- maybe that's it? Happy to bisect if necessary.
>
> FWIW I cannot reproduce the behavior you describe with commit 164555b4
> having some files in `org-agenda-files' with some tags.

Thanks for your reply. That's pretty weird! I just pulled and re-made,
and emacs -Q still does it, even with no Org agenda files defined. Just
a plain empty Agenda, then C-u r. I wish I knew what edebug was doing
with that org-let.

      reply	other threads:[~2016-01-17  6:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-16  2:19 Weirdness with Agenda and "C-u r" Eric Abrahamsen
2016-01-16  9:35 ` Marco Wahl
2016-01-17  6:03   ` Eric Abrahamsen [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=87ziw4wxnk.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).