From: Alexander Baier <alexander.baier@mailbox.org>
To: emacs-orgmode@gnu.org
Subject: Re: agenda configurable entry-text-mode
Date: Wed, 9 Aug 2017 21:39:11 +0200 [thread overview]
Message-ID: <omfocp$b33$1@blaine.gmane.org> (raw)
In-Reply-To: <87vamcdooq.fsf@alphapapa.net>
On 07/29/2017 03:20 AM, Adam Porter wrote:
> Alexander Baier <alexander.baier@mailbox.org> writes:
>
>> Hi Adam,
>>
>> I hadn't heard of org-quick-peek. I found
>> https://github.com/alphapapa/org-quick-peek but could not find the
>> package on MELPA, do you know why this is the case?
>
> Hi Alexander,
>
> Actually I haven't submitted it to MELPA yet. I've been hoping to get
> some more feedback and testing before doing that. I guess I should have
> adjusted the readme accordingly. I would appreciate if you could give
> it a quick test and let me know any feedback you may have. :)
This looks really nice! A few things I discovered:
1. If the peek contains a link and I click on it with the left mouse
button, the message "No link found" is displayed.
2. If a headline in the agenda contains a link to another headline and
point is somewhere on that headline and I call org-quick-peek-link I get
"Lisp error: (wrong-type-argument stringp nil)".
3. If point is on a link to another headline in a normal org buffer and
I call org-quick-peek-link I get "Lisp error: (void-variable path)".
This is fixed applying this patch:
@@ -80,7 +80,7 @@
(org-show-following-heading nil)
(org-show-entry-below nil)
(org-show-siblings nil)
- link type marker)
+ link type marker path)
;; From org.el
(when (and (looking-at org-complex-heading-regexp))
Regards,
--
Alex
next prev parent reply other threads:[~2017-08-09 19:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 9:30 agenda configurable entry-text-mode Alexander Baier
2017-07-25 18:08 ` Adam Porter
2017-07-28 12:26 ` Alexander Baier
2017-07-29 1:20 ` Adam Porter
2017-08-09 19:39 ` Alexander Baier [this message]
2017-08-09 22:46 ` Adam Porter
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='omfocp$b33$1@blaine.gmane.org' \
--to=alexander.baier@mailbox.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.