emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: phillip.lord@newcastle.ac.uk (Phillip Lord)
To: emacs-orgmode@gnu.org
Subject: Re: Lentic.0.6 and org mode
Date: Fri, 09 Jan 2015 19:18:50 +0000	[thread overview]
Message-ID: <87iogfyd7p.fsf@newcastle.ac.uk> (raw)

> On 2015-01-09 17:12, address@hidden (Phillip Lord) writes:
> 
> > It's configurable, though. By default, the two windows share the same
> > text (which is nearly the same behaviour as indirect buffers). But they
> > can also be different (but related). I use a file or dir-local variable
> > for this. So, the lentic source code uses:
> >
> > ((emacs-lisp-mode
> >   .
> >   ((lentic-init . lentic-orgel-org-init)
> >    (eval . (require 'm-buffer-macro)))))
> 
> I've used a similar configuration
> 
> #+begin_src emacs-lisp
> (add-hook 'emacs-lisp-mode-hook (lambda () (setq lentic-init 
> 'lentic-orgel-org-init)))
> #+end_src

Personally, I wouldn't do that! At the moment, my transformation doesn't
work nicely for all el files. At a minimum, you need code markers at the
before the first line of lisp and the after the last.

Otherwise, all the code gets treated by org as text; if you run, say,
"fill-paragraph" in the org-mode lentic view then it will do bad things 
when all the code gets refilled.


> 
> but it's not as nice as in the demo. For instance, the following:
> 
> #+begin_src emacs-lisp
> ;;; Code:
> 
> ;; ** Startup
> 
> ;; #+begin_src emacs-lisp
> 
> ;; Turn off mouse interface early in startup to avoid momentary display
> 
> (if (fboundp 'tool-bar-mode) (tool-bar-mode -1))
> (if (fboundp 'scroll-bar-mode) (scroll-bar-mode -1))
> #+end_src
> 
> becomes
> 
> #+begin_src org
> * Code
> 
> ;; ** Startup
> 
> ;; #+begin_src emacs-lisp
> 
> ;; Turn off mouse interface early in startup to avoid momentary display
> 
> (if (fboundp 'tool-bar-mode) (tool-bar-mode -1))
> (if (fboundp 'scroll-bar-mode) (scroll-bar-mode -1))
> #+end_src
> 
> Why the "Startup" is not promoted at the org level?

If your example is complete, I think it's because your code markers are
unbalanced. Look in the *lentic-log* buffer and you should see lots of
"delimiters do not match". Put a ";; #+end_src" in place and it should
fix itself.

This should probably be smoothed over in the user interface. I could
tell the user when the lentic buffer is created. You've also uncovered a
bug -- when the delimiters do not match, it's should be doing the safest
transformation of all which is a direct copy; so the "* Code" line
should have been left alone also.

Phil

             reply	other threads:[~2015-01-09 20:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09 19:18 Phillip Lord [this message]
2015-01-10 12:35 ` Lentic.0.6 and org mode Alan Schmitt
2015-01-15 15:54   ` Phillip Lord
2015-01-15 17:24     ` Alan Schmitt
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=87iogfyd7p.fsf@newcastle.ac.uk \
    --to=phillip.lord@newcastle.ac.uk \
    --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).