emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Alan Schmitt <alan.schmitt@polytechnique.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: org-src-fontification buffers
Date: Fri, 18 Mar 2016 11:40:49 -0400	[thread overview]
Message-ID: <87lh5fpzem.fsf@kyleam.com> (raw)
In-Reply-To: <m2io0jzw61.fsf@charm-wifi.irisa.fr> (Alan Schmitt's message of "Fri, 18 Mar 2016 15:40:38 +0100")

Alan Schmitt <alan.schmitt@polytechnique.org> writes:

> Hello,
>
> I'm having an issue with a buffer that is created by org for
> fontification that wants to be saved, although it's temporary. In my
> case, it's org-src-fontification:coq-mode, but it seems the problem
> happens for other languages (see
> https://emacs.stackexchange.com/questions/20593/org-src-fontify-natively-makes-magit-think-there-are-unsaved-files/20607)

Trying with elisp blocks, I'm not able to reproduce this (pretty recent
Emacs 25, GNU/Linux, latest Org).

How are you calling save-some-buffers?  It should ignore buffers that
aren't visiting files unless its PRED argument is non-nil or a function
that returns non-nil.

Can you step through save-some-buffers and see what's going on there?
Specifically, what's passed in as PRED and what happens here?

    (or (not (functionp pred))
        (with-current-buffer buffer (funcall pred)))

> Is there a way to tell emacs it's ok to kill this buffer without saving
> it?

We could `(set-buffer-modified-p nil)', which will force
save-some-buffers to ignore it, but I don't think that should be
necessary.

-- 
Kyle

      reply	other threads:[~2016-03-18 15:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-18 14:40 org-src-fontification buffers Alan Schmitt
2016-03-18 15:40 ` Kyle Meyer [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=87lh5fpzem.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=alan.schmitt@polytechnique.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 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).