On Jan 29, 2008, at 5:04 PM, Phil Jackson wrote:
Phil Jackson [EMAIL PROTECTED] writes:
Carsten Dominik [EMAIL PROTECTED] writes:
[...]
I *personally* still can't decide if this is within org's scope
though, not to say I wouldn't find it very handy.
So then am confused what you
Phil Jackson [EMAIL PROTECTED] writes:
Carsten Dominik [EMAIL PROTECTED] writes:
[...]
I *personally* still can't decide if this is within org's scope
though, not to say I wouldn't find it very handy.
So then am confused what you initial message was about. The feature
your are asking for
I'd like to see this too, primarily for HTML export (for syntax
highlighting etc) though it would be handy if you could also display the
syntax highlighting of the specified mode inside the block in Emacs.
Would it be practical to just specify the major mode to use with
htmlify in order to
Phil Jackson wrote:
Phil Jackson [EMAIL PROTECTED] writes:
Carsten Dominik [EMAIL PROTECTED] writes:
[...]
I *personally* still can't decide if this is within org's scope
though, not to say I wouldn't find it very handy.
So then am confused what you initial message was about. The
Russell Adams [EMAIL PROTECTED] writes:
I'd like to see this too, primarily for HTML export (for syntax
highlighting etc) though it would be handy if you could also display the
syntax highlighting of the specified mode inside the block in Emacs.
Would it be practical to just specify the
Phil Jackson [EMAIL PROTECTED] writes:
So what do you think Carsten? I would like to see the:
#+BEGIN_EXAMPLE lang:shell-script
#+END_EXAMPLE
That Bastien suggested. I would be willing to help out the exporter
people if need be.
For the record, the full suggestion is here:
Rick Moynihan [EMAIL PROTECTED] writes:
Also, Bastien... In blorg.el is it possible to include HTML snippets as
blocks of markup inside the posts? For example embedding a video into a
post?
Sadly not - but keep the pressure, it motivates me to work harder on the
next org-based blogging tool
On Jan 16, 2008, at 7:59 PM, Phil Jackson wrote:
Carsten Dominik [EMAIL PROTECTED] writes:
On Jan 8, 2008, at 12:22 PM, Phil Jackson wrote:
[...]
is the lack of a method to 'embed' source code into a document ala:
src lang=shell-script
...
/src
[...]
It seems to me that there are
Carsten Dominik [EMAIL PROTECTED] writes:
On Jan 16, 2008, at 7:59 PM, Phil Jackson wrote:
[...]
I *personally* still can't decide if this is within org's scope
though, not to say I wouldn't find it very handy.
So then am confused what you initial message was about. The feature
your are
On Jan 8, 2008, at 12:22 PM, Phil Jackson wrote:
Hi,
This may well be beyond the scope of Org but the only thing that keeps
me from switching everything from Muse to Org is the lack of a
method to
'embed' source code into a document ala:
src lang=shell-script
...
/src
Is this something
Carsten Dominik [EMAIL PROTECTED] writes:
On Jan 8, 2008, at 12:22 PM, Phil Jackson wrote:
[...]
is the lack of a method to 'embed' source code into a document ala:
src lang=shell-script
...
/src
[...]
It seems to me that there are really two issues here:
1. Font-locking in the
On Jan 8, 2008, at 8:04 PM, Eddward DeVilla wrote:
On Jan 8, 2008 8:03 AM, Bastien [EMAIL PROTECTED] wrote:
BTW, we had a discussion earlier with Carsten on whether the #+BEGIN*
directives formed a consistent class. I suggested to distinguish
between #+BEGIN_[export_language] and
I definite agree with that. I, too, primarily use org-mode for the
way things
look in Emacs. I occasionally export but my main use is within emacs.
Thanks,
Ed
I guess I'm missing the point. Optional tags to improve syntax
highlighting in code snippets or to improve export wouldn't
On Wed, Jan 09, 2008 at 11:50:20AM -0600, Russell Adams wrote:
I definite agree with that. I, too, primarily use org-mode for the
way things
look in Emacs. I occasionally export but my main use is within emacs.
Thanks,
Ed
Same here. A legible and easy to type .org format is very
Hi,
This may well be beyond the scope of Org but the only thing that keeps
me from switching everything from Muse to Org is the lack of a method to
'embed' source code into a document ala:
src lang=shell-script
...
/src
Is this something that might be possible in the future?
Cheers,
Phil
On Jan 8, 2008 8:03 AM, Bastien [EMAIL PROTECTED] wrote:
BTW, we had a discussion earlier with Carsten on whether the #+BEGIN*
directives formed a consistent class. I suggested to distinguish
between #+BEGIN_[export_language] and #+BEGIN_[type_of_region]. I
further suggested that we could
16 matches
Mail list logo
