From: Thomas Fitzsimmons <fitzsim@fitzsim.org>
To: "Sniffen\, Brian" <bsniffen@akamai.com>
Cc: 23765-done@debbugs.gnu.org
Subject: bug#23765: 24.5; exco-calendar-show-day calls user-error if org-startup-with-latex-preview
Date: Thu, 16 Jun 2016 22:13:54 -0400 [thread overview]
Message-ID: <m3mvmk7eal.fsf@fitzsim.org> (raw)
In-Reply-To: <63FD6454-A1BC-4B68-88BD-5F99F2C89A63@akamai.com> (Brian Sniffen's message of "Wed, 15 Jun 2016 16:08:56 +0000")
"Sniffen, Brian" <bsniffen@akamai.com> writes:
> ˘
>> On Jun 14, 2016, at 10:24 PM, Thomas Fitzsimmons <fitzsim@fitzsim.org> wrote:
>>
>> Hi Brian,
>>
>> "Brian T. Sniffen" <bsniffen@akamai.com> writes:
>>
>>> With org-startup-with-latex-preview set to non-nil, M-x excorporate, work
>>> through autoconfiguration, then M-x calendar. Hit 'e'. Get told
>>> "user-error: Can't preview LaTeX fragment in a non-file buffer".
>>>
>>> Unset org-startup-with-latex-preview, then go back to calendar and hit
>>> 'e'. See pretty org-mode calendar.
>>
>> Thanks for the report. I just pushed a fix, in Excorporate 0.7.4. It
>> should hit GNU ELPA overnight. Can you update and confirm it fixes the
>> bug?
>
> That works.
I noticed that with the fix, C-x s (save-some-buffers) always prompts
about *Excorporate*. I pushed 0.7.5 to prevent that (while still fixing
your issue). I'm marking this bug report as "done".
> Thanks for the great software; I’m excited about having one command to
> predict where I am, get the invitees, tell my phone to dial in, and
> give me a buffer for notes.
Sounds good; a feature I have planned (retrieve message body) should
help with some of these.
Thomas
prev parent reply other threads:[~2016-06-17 2:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 20:36 bug#23765: 24.5; exco-calendar-show-day calls user-error if org-startup-with-latex-preview Brian T. Sniffen
[not found] ` <m3h9cvqjd9.fsf@fitzsim.org>
[not found] ` <63FD6454-A1BC-4B68-88BD-5F99F2C89A63@akamai.com>
2016-06-17 2:13 ` Thomas Fitzsimmons [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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3mvmk7eal.fsf@fitzsim.org \
--to=fitzsim@fitzsim.org \
--cc=23765-done@debbugs.gnu.org \
--cc=bsniffen@akamai.com \
/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.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).