emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bill White <billw@wolfram.com>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Buffer *temp* modified; kill anyway?
Date: Wed, 04 Mar 2009 13:57:54 -0600	[thread overview]
Message-ID: <87d4cxf4cd.fsf@wolfram.com> (raw)
In-Reply-To: <9344.1236191912@alphaville.usa.hp.com> (Nick Dokos's message of "Wed, 04 Mar 2009 13:38:32 -0500")

On Wed Mar 04 2009 at 12:38, Nick Dokos <nicholas.dokos@hp.com> wrote:

> Bill White <billw@wolfram.com> wrote:
>
>> Hi all -
>> 
>> "Buffer  *temp* modified; kill anyway?" is driving me nuts.
>> 
>> Has anyone seen this error message when html-exporting pages that
>> contain #+begin_src ?  I get this once for every #+begin_src
>> ... #+end_src group on a page.  I assume it's coming from htmlize.el,
>> but I haven't been able to isolate the problem with edebug.  I'm using
>> the latest htmlize.el from
>> http://fly.srk.fer.hr/~hniksic/emacs/htmlize.el
>> 
>> Any ideas what's going on and how to silence it?  If it weren't for this
>> I'd be able to publish without babysitting the process through
>> source-heavy files.
>> 
>
> Bill,
>
> I just tried exporting the following:
>
> ,----
> | * Lisp source code
> | 
> | #+begin_src emacs-lisp
> | (defun org-xor (a b)
> |      "Exclusive or."
> |      (if a (not b) b))
> | #+end_src
> `----
>
> and did not have the problem you describe. Can you post a minimal example?

Here's one that triggers it:

,----
| * Lisp source code
| 
| #+begin_src message
| From: Nick Dokos <nicholas.dokos@hp.com>
| Subject: Re: [Orgmode] Buffer *temp* modified; kill anyway? 
| To: Bill White <billw@wolfram.com>
| Cc: emacs-orgmode@gnu.org
| Date: Wed, 04 Mar 2009 13:38:32 -0500 (from Gnus)
| Reply-To: nicholas.dokos@hp.com
| X-Sent: 1 hour, 9 minutes, 51 seconds ago
| Message-ID: <9344.1236191912@alphaville.usa.hp.com>
| #+end_src
`----

Interestingly, the message is not triggered when I use your example with
its "#+begin_src emacs-lisp", nor does "#+begin_src mma" trigger
it (using Tim Wichmann's mma.el).

My versions are:
 - Org-mode version 6.23trans
 - GNU Emacs 23.0.90.1 (i686-pc-linux-gnu, GTK+ Version 2.12.9) of 2009-02-14 on billw-desktop
 - htmlize-version 1.34
 - message.el version 1.169 (from the emacs cvs checkout above)

Thanks for the example - I didn't realize that some src modes didn't
trigger the problem.

Cheers -

bw
-- 
Bill White . billw@wolfram.com . http://members.wolfram.com/billw
"No ma'am, we're musicians."

  reply	other threads:[~2009-03-04 19:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-04 17:26 Buffer *temp* modified; kill anyway? Bill White
2009-03-04 18:38 ` Nick Dokos
2009-03-04 19:57   ` Bill White [this message]
2009-03-04 21:47     ` Nick Dokos
2009-03-04 22:26       ` Nick Dokos
2009-03-05  4:55         ` Bill White

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=87d4cxf4cd.fsf@wolfram.com \
    --to=billw@wolfram.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.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/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).