emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Richard G Riley <rileyrgdev@googlemail.com>
To: Carsten Dominik <dominik@uva.nl>
Cc: org-mode <emacs-orgmode@gnu.org>,
	Richard G Riley <rileyrgdev@googlemail.com>
Subject: Re: html publish/export
Date: Tue, 15 Jul 2008 00:43:30 +0200	[thread overview]
Message-ID: <n4bq103x4d.fsf@richardriley.net> (raw)
In-Reply-To: <D52E3074-74F0-4619-B957-555A9FB73EAC@uva.nl> (Carsten Dominik's message of "Mon, 14 Jul 2008 11:34:06 -0700")

Carsten Dominik <dominik@uva.nl> writes:

> On Jul 14, 2008, at 9:18 AM, Richard G Riley wrote:
>
>>
>> Is it possible for the publish functions to work without actually
>> opening published files into buffers? I get a lot of buffers opening
>> and
>> closing and often disappearing altogether (ie closed) after a
>> publish -
>> even though I was in that file and editing it before I published. In
>> addition, opening the files into "visible" buffers triggers mode
>> specifics to kick in like nxhtml mode which significantly increases
>> the
>> publish time. Is it necessary?
>
> Hi Richard,
>
> I don't the why you'd want to hand-edit a file that is automatically
> created
> by the publishing process, so I don't really understand that part.

I meant it opens the other project org files as buffers. In addition, I
guess it creates temporary "real buffers" for its exported html files -
it is these that trigger the nxhtml load etc.

Frequently the org file I was editing when I publish is closed by the
publish functions.

>
> I guess we could avoid setting nxhtml mode for the created files and
> remove the buffers when publishing.
>
> - Carsten

  reply	other threads:[~2008-07-14 22:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 16:18 html publish/export Richard G Riley
2008-07-14 18:34 ` Carsten Dominik
2008-07-14 22:43   ` Richard G Riley [this message]
2008-07-14 22:51     ` Carsten Dominik

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=n4bq103x4d.fsf@richardriley.net \
    --to=rileyrgdev@googlemail.com \
    --cc=dominik@uva.nl \
    --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).