From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: Phillip Lord <phillip.lord@newcastle.ac.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: Lentic.0.6 and org mode
Date: Thu, 15 Jan 2015 18:24:44 +0100 [thread overview]
Message-ID: <m28uh45543.fsf@charm-ecran.irisa.fr> (raw)
In-Reply-To: <87y4p482f2.fsf@newcastle.ac.uk> (Phillip Lord's message of "Thu, 15 Jan 2015 15:54:41 +0000")
[-- Attachment #1: Type: text/plain, Size: 1601 bytes --]
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:
--8<---------------cut here---------------start------------->8---
;;; lentic_test --- testing it
;;; Commentary:
;; this is a test
;;; Code:
;; a comment
;; ** a subsection
;; #+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
--8<---------------cut here---------------end--------------->8---
The last line is not nicely typeset.
>> By the way, what is the correct way of exiting lentic mode? For the
>> moment I kill the buffer and the window, but it would be nice to have
>> a function that exits lentic.
>
> 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.
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 494 bytes --]
next prev parent reply other threads:[~2015-01-15 17:24 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 [this message]
2015-01-15 22:28 ` Phillip Lord
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:
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=m28uh45543.fsf@charm-ecran.irisa.fr \
--to=alan.schmitt@polytechnique.org \
--cc=emacs-orgmode@gnu.org \
--cc=phillip.lord@newcastle.ac.uk \
/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).