emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: phillip.lord@newcastle.ac.uk (Phillip Lord)
To: Alan Schmitt <alan.schmitt@polytechnique.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Lentic.0.6 and org mode
Date: Thu, 15 Jan 2015 22:28:59 +0000	[thread overview]
Message-ID: <87wq4n3cgk.fsf@newcastle.ac.uk> (raw)
In-Reply-To: <m28uh45543.fsf@charm-ecran.irisa.fr> (Alan Schmitt's message of "Thu, 15 Jan 2015 18:24:44 +0100")

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

> On 2015-01-15 15:54, phillip.lord@newcastle.ac.uk (Phillip Lord) writes:
>> Good. If you find any examples which fail, I'd be happy to look.
> It's not really failing, but I don't know how to put the end of file
> markers so that lentic likes it. For instance:
> ;; #+begin_src emacs-lisp
> (message "foo")
> ;; #+end_src
> ;; #+begin_src emacs-lisp
> (provide 'lentic_test)
> ;; #+end_src
> ;; # Local Variables:
> ;; # lentic-init: lentic-orgel-org-init
> ;; # End:
> ;;; lentic_test.el ends here
> The last line is not nicely typeset.

So, local variables comes *after* the ends here line. Currently, the
"ends here" line needs to be *inside* a source block, so you would have...

;; #+begin_src emacs-lisp
(message "foo")
;; #+end_src

;; #+begin_src emacs-lisp
(provide 'lentic_test)
;;; lentic_test.el ends here
;; #+end_src

;; # Local Variables:
;; # lentic-init: lentic-orgel-org-init
;; # End:

I am debating the last bit. I could treat the last line specially, as I
do the first, so it would end up as

# # lentic_test.el ends here

in the org-mode version. But then it would not appear in the any
org-mode output when perhaps it should.

>> At the moment, killing one or the other lentic buffers does the job.
>> Lentic checks for the killed buffer and all should be good. An "exit
>> lentic" command might be nice, indeed. It could close all lentic buffers
>> except the first (currently lentic only supports one buffer, but
>> eventually it should support many). But killing the buffer works fine
>> also.
> Right now it's a three steps process:
> - kill the buffer
> - confirm the kill as it's modified (the "org" buffer)
> - close the window
> This is why I think a lentic-exit command would be great.

Ah, okay. Currently, the save-buffer command in the org lentic view
should also save the .el version (I have the two hooked together). I was
thinking of adding two new features -- an auto-delete capability, so
that the file associated with the org-mode version is deleted when the
buffer is closed (or Emacs exists). This is to stop leaving lots of org
files around the place.

The process would then be

- save-buffer
- kill-buffer

I could also modify kill-buffer so that iff auto-delete is set, the
modification will not trigger save requests.

Can I ask, why do you want to kill the buffer? Why not just bury it?


  reply	other threads:[~2015-01-15 22:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09 19:18 Lentic.0.6 and org mode Phillip Lord
2015-01-10 12:35 ` Alan Schmitt
2015-01-15 15:54   ` Phillip Lord
2015-01-15 17:24     ` Alan Schmitt
2015-01-15 22:28       ` Phillip Lord [this message]
2015-01-16 10:15         ` Alan Schmitt
2015-01-16 11:01           ` Phillip Lord
  -- strict thread matches above, loose matches on Subject: below --
2015-01-09 17:12 Phillip Lord
2015-01-09 17:57 ` Alan Schmitt
2015-01-08 13:55 Phillip Lord
2015-01-08 22:24 ` Thierry Banel
2015-01-11 12:33   ` joakim
2015-01-15 16:11     ` Phillip Lord
2015-01-15 20:53       ` Thierry Banel
2015-01-15 22:41         ` Phillip Lord
2015-01-16 18:43           ` Thierry Banel
2015-01-16 20:18             ` Thomas S. Dye
2015-01-16 23:46               ` Phillip Lord

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:

  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=87wq4n3cgk.fsf@newcastle.ac.uk \
    --to=phillip.lord@newcastle.ac.uk \
    --cc=alan.schmitt@polytechnique.org \
    --cc=emacs-orgmode@gnu.org \


* 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


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).