Carsten Dominik <[EMAIL PROTECTED]> writes:
> How about adding
>
> .src { overflow:auto }
>
> to the CSS style definitions? Is that what you are looking for? It
> seems to me that a scroll bar is better than wrapping, because source
> code is usually formatted the way it is for a reason.
>
> - Carsten
Yes, this is a good idea ( I didnt know of the overflow property to be
honest).
But I would still suggest one tiny amendment - the export could also wrap
source code in a src type specific div in addition to the general src
div. Hence we can easily add CSS information specific to the stated src
type in addition to the base src class.
e.g
where I have in my org file:
#+INCLUDE: "~/.emacs.d/init.el" src emacs-lisp
the resulting html is
<div class="src">
<div class="src-emacs-lisp">
..
..
or something similar which someone more experienced with CSS can
recommend.
cheers,
r.
>
> On Jul 12, 2008, at 11:07 AM, Richard G Riley wrote:
>
>>
>> is it possible to tell the exporter to wrap src code? e.g in this
>>
>> ,----
>> | #+HTML: <div id="Content">
>> | #+INCLUDE: "~/.emacs.d/init.el" src emacs-lisp
>> | [[../][Back]]
>> | #+HTML: </div>
>> `----
>>
>> some lines in the htmlized source code extends out beyond the
>> containing
>> div.
>>
>>
>>
>>
>>
>> _______________________________________________
>> 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
_______________________________________________
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
