emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: Matthew Lundin <mdl@imapmail.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org-publish - too many index.org files
Date: Sun, 2 Nov 2008 17:15:33 +0100	[thread overview]
Message-ID: <C5ED2E3C-32E1-4229-B9E6-8DF5A6E4FB6F@uva.nl> (raw)
In-Reply-To: <m263n6t96b.fsf@fastmail.fm>

Hi Matthew,

I hope this is fixed now.  Let me know what you find.

Best wishes.

- Carsten

On Nov 2, 2008, at 4:54 PM, Matthew Lundin wrote:

>
> Hi Carsten,
>
> Yes, I can confirm that turning off auto index resulted in the buffers
> being closed after publishing.
>
> Thanks,
> Matt
>
>
> Carsten Dominik <dominik@science.uva.nl> writes:
>
>> Hi Matthew,
>>
>> if you turn off the auto-index, do the buffers then disappear?
>>
>> Thanks for checking this out.
>>
>> - Carsten
>>
>> On Nov 2, 2008, at 1:50 PM, Matthew Lundin wrote:
>>
>>>
>>> Hi Carsten,
>>>
>>> Carsten Dominik <dominik@science.uva.nl> writes:
>>>
>>>> Hi Matthew,
>>>>
>>>> what org version are you using?
>>>>
>>>> Because I believe that in the current version, those buffers will  
>>>> be
>>>> killed, if they have been visited to get published.  Only buffers
>>>> which are already present  then starting the publishing will not be
>>>> killed.
>>>>
>>>> At least this is how it should work.
>>>
>>> I am using Org-mode 6.10c. I just did a test. I started up emacs  
>>> with
>>> no file buffers loaded. I then ran M-x org-publish RET project-name.
>>> After the project was published, my buffer menu contained all the  
>>> org
>>> files in the project.
>>>
>>> Here is my org-publish-project-alist configuration:
>>>
>>> (setq org-publish-project-alist
>>>     '(
>>> 	("org-notes"
>>> 	 :base-directory "~/mystuff/website/"
>>> 	 :base-extension "org"
>>> 	 :publishing-directory "[ssh to my site here]"
>>> 	 :section-numbers nil
>>> 	 :email "[my email address here]"
>>> 	 :publishing-function org-publish-org-to-html
>>> 	 :recursive t
>>> 	 :auto-index t
>>> 	 :style "<link rel=\"stylesheet\" type=\"text/css\"
>>> href=\"css/ myorg.css\" />"
>>> 	 :preamble "<div id=\"menu\">
>>> <ul>
>>> <li> <a href=\"index.html\">Home</a> </li>
>>> <li> <a href=\"sitemap.html\">Site Map</a> </li>
>>> <li> <a id=\"ie\" href=\"#\">Top of Page</a> </li>
>>> </ul>
>>> </div>"
>>> 	 :index-filename "pagelist.org"
>>> 	 :index-title "Page List"
>>> 	 :link-validation-function org-publish-validate-link
>>> 	 )
>>> 	("org-static"
>>> 	 :base-directory "~/mystuff/website/"
>>> 	 :publishing-directory "[ssh to my site here]"
>>> 	 :recursive t
>>> 	 :base-extension "css\\|js\\|png\\|jpg\\|gif\\|pdf\\|mp3\\|ogg\\| 
>>> swf"
>>> 	 :publishing-function org-publish-attachment
>>> 	 )
>>> 	("org"
>>> 	 :components
>>> 	 ("org-notes" "org-static"))
>>> 	))
>>>
>>> My apologies in advance if I goofed something up in the  
>>> configuration.
>>>
>>> Thanks,
>>> Matt
>>>
>>>
>>>> On Oct 30, 2008, at 4:04 PM, Matthew Lundin wrote:
>>>>
>>>>>
>>>>> I am setting up my website with multiple subdirectories, each, of
>>>>> course, with its own index.org (index.html) file.
>>>>>
>>>>> A problem arises when I invoke org-publish (or org-agenda). All of
>>>>> the
>>>>> org files in the project are loaded into buffers resulting in too
>>>>> many
>>>>> index.org files in my buffer list.
>>>>>
>>>>> 1) Is there any way to have org-publish close buffers after
>>>>> publishing
>>>>> the files?
>>>>>
>>>>> 2) Alternatively, is there an easy way to rename the buffers to  
>>>>> the
>>>>> title of the page designated with #+TITLE so that they can be told
>>>>> apart in the buffer list.
>>>>>
>>>>> ----
>>>>>
>>>>> Finally, on a related question. Does someone know an easy way to
>>>>> have
>>>>> all the org-files of subdirectories of a website added to the  
>>>>> agenda
>>>>> files recursively?
>>>>>
>>>>> For my agenda files I currently use:
>>>>>
>>>>> (setq org-agenda-files (file-expand-wildcards "~/org/*org"))
>>>>>
>>>>> That, however, only works for a single directory, not recursively.
>>>>>
>>>>> Thanks!
>>>>>
>>>>> Matt Lundin
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Emacs-orgmode mailing list
>>>>> Remember: use `Reply All' to send replies to the list.
>>>>> Emacs-orgmode@gnu.org
>>>>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

      reply	other threads:[~2008-11-02 16:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30 15:04 Org-publish - too many index.org files Matthew Lundin
2008-10-30 15:15 ` Richard Riley
2008-11-01 13:17   ` Carsten Dominik
2008-10-30 15:46 ` R: " Giovanni Ridolfi
2008-10-31  4:34   ` Matthew Lundin
2008-11-01  2:29 ` Ethan Blanton
2008-11-01  3:25   ` Matthew Lundin
2008-11-01 13:15 ` Carsten Dominik
2008-11-02 12:50   ` Matthew Lundin
2008-11-02 14:25     ` Carsten Dominik
2008-11-02 15:54       ` Matthew Lundin
2008-11-02 16:15         ` Carsten Dominik [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=C5ED2E3C-32E1-4229-B9E6-8DF5A6E4FB6F@uva.nl \
    --to=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=mdl@imapmail.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).