Sébastien Vauban writes:
> Hi,
>
> Dan Davison wrote:
>>> Please see the manual as an example.
>>
>> Hmm? The manual is written in texinfo.
>
> BTW, what's the reason for that? Does it still apply? Are there good reasons
> not to move it to Org format?
>
> Best regards,
> Seb
It does still a
Sébastien Vauban writes:
Hi, Seb
>> The manual is written in texinfo.
>
> BTW, what's the reason for that? [...]
> Are there good reasons
> not to move it to Org format?
Carsten wrote ;-) :
"Org-mode is currently not able to produce TeXInfo,
which is the standard for Emacs documentation.
A
Hi,
Dan Davison wrote:
>> Please see the manual as an example.
>
> Hmm? The manual is written in texinfo.
BTW, what's the reason for that? Does it still apply? Are there good reasons
not to move it to Org format?
Best regards,
Seb
--
Sébastien Vauban
_
On Thu, Jan 20, 2011 at 1:46 PM, Eric Schulte wrote:
> Jeff Horn writes:
>
>> On Thu, Jan 20, 2011 at 11:16 AM, Nick Dokos wrote:
>>> Matt Lundin wrote:
>>>
Nick Dokos writes:
> Matt Lundin wrote:
>
>> So the new, "flat" FAQ is up and running. And, of course, all are
Jeff Horn writes:
> On Thu, Jan 20, 2011 at 11:16 AM, Nick Dokos wrote:
>> Matt Lundin wrote:
>>
>>> Nick Dokos writes:
>>>
>>> > Matt Lundin wrote:
>>> >
>>> >> So the new, "flat" FAQ is up and running. And, of course, all are
>>> >> welcome to suggest or contribute further refinements.
>>>
>
> I see this issue a lot on the Babel pages. What needs to be done is
> wrap each source/example block in another block with "org" as the
> language.
>
> For example:
>
> #+begin_src org
> ,#+begin_src sh :results output
> ls -al
> ,#+end_src
> #+end_src
>
> I think this should be done f
On Thu, Jan 20, 2011 at 11:16 AM, Nick Dokos wrote:
> Matt Lundin wrote:
>
>> Nick Dokos writes:
>>
>> > Matt Lundin wrote:
>> >
>> >> So the new, "flat" FAQ is up and running. And, of course, all are
>> >> welcome to suggest or contribute further refinements.
>> >>
>> >
>> > Blue (or purple or
Matt Lundin wrote:
> Nick Dokos writes:
>
> > Matt Lundin wrote:
> >
> >> So the new, "flat" FAQ is up and running. And, of course, all are
> >> welcome to suggest or contribute further refinements.
> >>
> >
> > Blue (or purple or similar color) text on black background is unreadable -
> > at
On Thu, Jan 20, 2011 at 12:48 PM, Dan Davison wrote:
> On Thu, Jan 20, 2011 at 5:41 PM, Dan Davison wrote:
>> On Thu, Jan 20, 2011 at 5:02 PM, Jeff Horn wrote:
>>>
>>> On Thu, Jan 20, 2011 at 6:22 AM, Dan Davison wrote:
>>> > I strongly second this. In fact I'll stick my neck out more: Worg is
On Thu, Jan 20, 2011 at 5:41 PM, Dan Davison wrote:
> On Thu, Jan 20, 2011 at 5:02 PM, Jeff Horn wrote:
>>
>> On Thu, Jan 20, 2011 at 6:22 AM, Dan Davison wrote:
>> > I strongly second this. In fact I'll stick my neck out more: Worg is
>> > great, but for tutorials on org-mode, HTML export is of
On Thu, Jan 20, 2011 at 12:41 PM, Dan Davison wrote:
> All of which could be solved with some effort. My point is: what does
> the HTML export of this document really offer over the verbatim
> htmlized one?
I'll concede. I seem to have spoken out of turn, since I haven't
authored any tutorials, a
Jeff Horn writes:
> On Thu, Jan 20, 2011 at 6:22 AM, Dan Davison wrote:
>> I strongly second this. In fact I'll stick my neck out more: Worg is
>> great, but for tutorials on org-mode, HTML export is often the wrong
>> format for obvious reasons (i.e. unless you go to some trouble, it
>> conceal
On Thu, Jan 20, 2011 at 5:02 PM, Jeff Horn wrote:
>
> On Thu, Jan 20, 2011 at 6:22 AM, Dan Davison wrote:
> > I strongly second this. In fact I'll stick my neck out more: Worg is
> > great, but for tutorials on org-mode, HTML export is often the wrong
> > format for obvious reasons (i.e. unless y
Erik Iverson writes:
> Jeff Horn wrote:
>> On Thu, Jan 20, 2011 at 6:22 AM, Dan Davison wrote:
>>> I strongly second this. In fact I'll stick my neck out more: Worg is
>>> great, but for tutorials on org-mode, HTML export is often the wrong
>>> format for obvious reasons (i.e. unless you go to s
Jeff Horn wrote:
On Thu, Jan 20, 2011 at 6:22 AM, Dan Davison wrote:
I strongly second this. In fact I'll stick my neck out more: Worg is
great, but for tutorials on org-mode, HTML export is often the wrong
format for obvious reasons (i.e. unless you go to some trouble, it
conceals a lot of t
On Thu, Jan 20, 2011 at 6:22 AM, Dan Davison wrote:
> I strongly second this. In fact I'll stick my neck out more: Worg is
> great, but for tutorials on org-mode, HTML export is often the wrong
> format for obvious reasons (i.e. unless you go to some trouble, it
> conceals a lot of the org syntax)
On Thu, Jan 20, 2011 at 11:44 AM, Eric Schulte wrote:
> For managing alternate stylesheets I use the "style chooser" extension
> for Chrome which adds a dropdown menu to the url-bar whenever a page
> provides alternate style sheets and has the nice feature of remembering
> your last selection for
Bastien writes:
> Jason Dunsmore writes:
>
>> There's a Firefox add-on that will give you configurable per-site user
>> CSS:
>> https://addons.mozilla.org/en-US/firefox/addon/stylish/
>
> I installed this but AFAIK it doesn't help managing alternative
> stylesheets as defined by the headers of t
Matt Lundin writes:
> Nick Dokos writes:
>
>> Matt Lundin wrote:
>>
>>> So the new, "flat" FAQ is up and running. And, of course, all are
>>> welcome to suggest or contribute further refinements.
>>>
>>
>> Blue (or purple or similar color) text on black background is unreadable -
>> at least t
Nick Dokos writes:
> Matt Lundin wrote:
>
>> So the new, "flat" FAQ is up and running. And, of course, all are
>> welcome to suggest or contribute further refinements.
>>
>
> Blue (or purple or similar color) text on black background is unreadable -
> at least to my eyes.
I agree. I reverted t
Jeff Horn writes:
> On Wed, Jan 19, 2011 at 9:24 PM, Matt Lundin wrote:
>> I believe these pages have not been exported since we turned off the
>> inline css publishing option; i.e., they have not been touched since
>> that time, so the publishing mechanism does not export them.
>
> Matt,
>
> I
Jason Dunsmore writes:
> "Eric Schulte" writes:
>
>> Matt Lundin writes:
>>
>>> Bastien writes:
>>>
Jeff Horn writes:
> Jason seems to be garnering a lot of votes, but Eric's zenburn
> emulation makes my eyes happy. If Jason wins out, I suppose I could
> always just read
On Wed, Jan 19, 2011 at 9:24 PM, Matt Lundin wrote:
> I believe these pages have not been exported since we turned off the
> inline css publishing option; i.e., they have not been touched since
> that time, so the publishing mechanism does not export them.
Matt,
I was going to grep through the r
Matt Lundin wrote:
> So the new, "flat" FAQ is up and running. And, of course, all are
> welcome to suggest or contribute further refinements.
>
Blue (or purple or similar color) text on black background is unreadable -
at least to my eyes.
Thanks,
Nick
_
"Eric Schulte" writes:
> I just pushed up an edit to the Worg repository which should reset all
> of the defaults on the TOC of the org-faq-nojs.org page. If this works
> I vote we set this as the sole org-faq page.
I agree. I went ahead and did the following:
$ mv org-faq-nojs.org org-faq.org
Jason Dunsmore writes:
> Does anybody know why some pages have inline CSS? For example:
>
...
> I came across this when trying to figure out what was causing the
> different H1 styles (top page title). For example, compare:
>
> http://orgmode.org/worg/org-faq-nojs.html
> and
> http://orgmode.or
On Wed, Jan 19, 2011 at 1:32 PM, Jason Dunsmore
wrote:
> Jeff Horn writes:
>
>> On Wed, Jan 19, 2011 at 12:34 PM, Jason Dunsmore
>> wrote:
>>> I think this might be unnecessary (hitting "Back", typing the "Home"
>>> key, or middle clicking at the top of the scroll bar can all already do
>>> this
On Wed, Jan 19, 2011 at 2:18 PM, Jason Dunsmore
wrote:
> Does anybody know why some pages have inline CSS? For example:
The publishing projects for the affected pages may not have the the
:style-default key set to "nil". The relevant variable is
`org-export-html-style-include-default`.
--
Jeff
10:46:14 AM
Subject: Re: [Orgmode] Re: Worg needs some reorganizing
On Tue, Jan 18, 2011 at 3:39 AM, Bastien wrote:
> Jeff Horn writes:
>
>> Jason seems to be garnering a lot of votes, but Eric's zenburn
>> emulation makes my eyes happy. If Jason wins out, I suppose I co
Achim Gratz writes:
> Jason Dunsmore writes:
>> Looks like the TOC links are larger than the text on the rest of the
>> page. Can the text size be made the same?
>
> That's what the "inherit" is fixing. You may still have the old copy in
> cache, I've just now been able to get the new version
Jason Dunsmore writes:
> Looks like the TOC links are larger than the text on the rest of the
> page. Can the text size be made the same?
That's what the "inherit" is fixing. You may still have the old copy in
cache, I've just now been able to get the new version that Eric pushed
some time ago.
"Eric Schulte" writes:
> Achim Gratz writes:
>
>> "Eric Schulte" writes:
>>> I just pushed up an edit to the Worg repository which should reset all
>>> of the defaults on the TOC of the org-faq-nojs.org page. If this works
>>> I vote we set this as the sole org-faq page.
>>
>> It works, but I
Jason Dunsmore writes:
> And there's something in the CSS 2.1 spec about allowing users to attach
> style sheets that I don't fully understand.
> http://www.w3.org/TR/CSS21/
That's quite likely the user stylesheets. Support for this is generally
bad, even on Firefox you'll have to re-start for e
Jeff Horn writes:
> On Wed, Jan 19, 2011 at 12:34 PM, Jason Dunsmore
> wrote:
>> I think this might be unnecessary (hitting "Back", typing the "Home"
>> key, or middle clicking at the top of the scroll bar can all already do
>> this).
>
> I'm not an expert, but that is not very "accessible". Sho
Achim Gratz writes:
> "Eric Schulte" writes:
>> I just pushed up an edit to the Worg repository which should reset all
>> of the defaults on the TOC of the org-faq-nojs.org page. If this works
>> I vote we set this as the sole org-faq page.
>
> It works, but I think you would want
>
> font-size
"Eric Schulte" writes:
> I just pushed up an edit to the Worg repository which should reset all
> of the defaults on the TOC of the org-faq-nojs.org page. If this works
> I vote we set this as the sole org-faq page.
It works, but I think you would want
font-size: inherit;
in the first block.
On Wed, Jan 19, 2011 at 12:34 PM, Jason Dunsmore
wrote:
> I think this might be unnecessary (hitting "Back", typing the "Home"
> key, or middle clicking at the top of the scroll bar can all already do
> this).
I'm not an expert, but that is not very "accessible". Shouldn't be a
problem with moder
Bastien writes:
> I changed the background of code chunks to black - please revert this
> if you find it too agressive/unreadable. I really dislike the fake
> white we had as the background for black-on-white code chunks...
If you change the background you'll also need to change all the
foregr
>> On this one page, I think we need a simple (non-js) table-of-contents.
>> Is there a way to override the hidden toc for this page only?
>
> I agree (copying Eric on this email - he might know).
>
I just pushed up an edit to the Worg repository which should reset all
of the defaults on the TOC o
Matt Lundin writes:
> Jason Dunsmore writes:
>
>> I made a version of the FAQ without the javascript folding:
>>
>> http://orgmode.org/tmp/worg/org-faq-nojs.html
>> http://orgmode.org/tmp/worg/org-faq.html
>>
>> It like it better, but it's still a bit unwieldy. Maybe the FAQ just
>> needs to be
Achim Gratz writes:
> Matt Lundin writes:
>> On this one page, I think we need a simple (non-js) table-of-contents.
>> Is there a way to override the hidden toc for this page only?
>
> Yes, by either adding a stylesheet that undoes the hiding or by not
> including the part of the stylesheet tha
Matt Lundin writes:
> On this one page, I think we need a simple (non-js) table-of-contents.
> Is there a way to override the hidden toc for this page only?
Yes, by either adding a stylesheet that undoes the hiding or by not
including the part of the stylesheet that hides the toc in the first
pl
Bastien writes:
> I don't have a strong opinion about this: splitting the FAQ into
> org-faq-*.org comes to my mind, but it's a big task. org-info-js,
> while not optimal for *every* page on Worg, was doing a good job
> on the FAQ.
Maybe this delivers motivation to incorporate a little impro
On Tue, Jan 18, 2011 at 8:21 PM, Bastien wrote:
> Jason Dunsmore writes:
>
>> There's a Firefox add-on that will give you configurable per-site user
>> CSS:
>> https://addons.mozilla.org/en-US/firefox/addon/stylish/
>
> I installed this but AFAIK it doesn't help managing alternative
> stylesheets
On Tue, Jan 18, 2011 at 5:42 PM, Eric Schulte wrote:
>> I don't have a strong opinion about this: splitting the FAQ into
>> org-faq-*.org comes to my mind, but it's a big task. org-info-js,
>> while not optimal for *every* page on Worg, was doing a good job
>> on the FAQ.
>
> I'd lean towards kee
Jason Dunsmore writes:
> There's a Firefox add-on that will give you configurable per-site user
> CSS:
> https://addons.mozilla.org/en-US/firefox/addon/stylish/
I installed this but AFAIK it doesn't help managing alternative
stylesheets as defined by the headers of the HTML page itself...
Thank
Bastien writes:
> Jason Dunsmore writes:
>
>> The new stylesheet is in place now.
>
> Great, thanks all for this effort!
Yes, many thanks!
> I changed the background of code chunks to black - please revert this
> if you find it too agressive/unreadable. I really dislike the fake
> white we
Bastien writes:
> Jason Dunsmore writes:
>
>> I added the following to org-publish-project-alist:
>>
>> ("worg-htmlize"
>> :base-directory "~/git/Worg/"
>> :base-extension "org"
>> :html-extension "org.html"
>> :publishing-directory "/var/www/orgmode.o
Jason Dunsmore writes:
> I made a version of the FAQ without the javascript folding:
>
> http://orgmode.org/tmp/worg/org-faq-nojs.html
> http://orgmode.org/tmp/worg/org-faq.html
>
> It like it better, but it's still a bit unwieldy. Maybe the FAQ just
> needs to be reorganized. See how Wikipedia
Bernt Hansen writes:
> and I use this :)
>
> :publishing-function (org-publish-org-to-html
> org-publish-org-to-org)
> :plain-source t
> :htmlized-source t
Cool. I setup this on the server (except the :plain-source t).
Thanks,
--
Bastien
___
> I changed the background of code chunks to black - please revert this
> if you find it too agressive/unreadable. I really dislike the fake
> white we had as the background for black-on-white code chunks...
I just replaced the black with a slightly softer dark-gray, please feel
free to revert.
Jason Dunsmore writes:
> The new stylesheet is in place now.
Great, thanks all for this effort!
Jason, correct me if I'm wrong, I think you copied worg.css directly on
the server. So I put it in the Worg.git repo and then publised Worg
again.
So changes to worg.css can happen from the repo (u
Jason Dunsmore writes:
> Matt Lundin writes:
>
>> Bastien writes:
>>
>>> Jeff Horn writes:
>>>
Jason seems to be garnering a lot of votes, but Eric's zenburn
emulation makes my eyes happy. If Jason wins out, I suppose I could
always just read Worg in emacs... :D
>>>
>>> Or use E
Bastien writes:
> Jason Dunsmore writes:
>
>> I added the following to org-publish-project-alist:
>>
>> ("worg-htmlize"
>> :base-directory "~/git/Worg/"
>> :base-extension "org"
>> :html-extension "org.html"
>> :publishing-directory "/var/www/orgmode.o
Matt Lundin writes:
> Bastien writes:
>
>> Jeff Horn writes:
>>
>>> Jason seems to be garnering a lot of votes, but Eric's zenburn
>>> emulation makes my eyes happy. If Jason wins out, I suppose I could
>>> always just read Worg in emacs... :D
>>
>> Or use Eric zenburn-like css by selecting it
> I don't have a strong opinion about this: splitting the FAQ into
> org-faq-*.org comes to my mind, but it's a big task. org-info-js,
> while not optimal for *every* page on Worg, was doing a good job
> on the FAQ.
I'd lean towards keep the FAQ as one large flat html file to encourage
text s
Jason Dunsmore wrote:
> > I don't have a strong opinion about this: splitting the FAQ into
> > org-faq-*.org comes to my mind, but it's a big task. org-info-js,
> > while not optimal for *every* page on Worg, was doing a good job
> > on the FAQ.
>
> Sometimes I come across one of those huge j
Bastien writes:
> Jason Dunsmore writes:
>
>> I made a version of the FAQ without the javascript folding:
>>
>> http://orgmode.org/tmp/worg/org-faq-nojs.html
>> http://orgmode.org/tmp/worg/org-faq.html
>
> Thanks. Nitpicking: I'd prefer paragraphs to be indented to the right
> (so that headines
Jason Dunsmore writes:
> I added the following to org-publish-project-alist:
>
> ("worg-htmlize"
> :base-directory "~/git/Worg/"
> :base-extension "org"
> :html-extension "org.html"
> :publishing-directory "/var/www/orgmode.org/worg/"
> :recurs
Jason Dunsmore writes:
> I made a version of the FAQ without the javascript folding:
>
> http://orgmode.org/tmp/worg/org-faq-nojs.html
> http://orgmode.org/tmp/worg/org-faq.html
Thanks. Nitpicking: I'd prefer paragraphs to be indented to the right
(so that headines are always left from the text
Jason Dunsmore writes:
>> While we're fixing things, are there any objections to making the
>> publishing change recommended above? It should significantly reduce the
>> size of pages which contain a large amount of source code, and will make
>> it easier to adjust the fontification inside of co
Matt Lundin writes:
>> My suggestion would be to go with Jason's css (combined with Eric's
>> expandable table of contents) then have Eric's css and the old-worg
>> css available as alternative css.
>
> I like Jason's stylesheet, and have a couple of observations:
>
> 1) h3 headers are indented,
Jason Dunsmore writes:
> "Eric Schulte" writes:
>
By the way, having the javascript section-folding enabled on only some
pages is confusing and doesn't make for the best browsing experience.
Now that the TOC will be collapsed by default, perhaps it's no longer
needed?
>>
On Tue, Jan 18, 2011 at 1:50 PM, Jason Dunsmore
wrote:
> I get the error "Symbol's function definition is void: publish-htmlize".
> I made sure to (require 'htmlize).
I believe the function `org-publish-org-to-org` calls htmlize. Make
sure to (require 'org-publish).
--
Jeffrey Horn
http://www.f
"Eric Schulte" writes:
>>
>> One last change I would suggest, is that rather than use inline css for
>> the highlighted source code, we use a css stylesheet by setting the
>>
>> (setq org-export-htmlize-output-type 'css)
>>
>> Then use a single .css style sheet as done with the "@import(emacs.
"Eric Schulte" writes:
> Matt Lundin writes:
>
>> Bastien writes:
>>
>>> Jeff Horn writes:
>>>
Jason seems to be garnering a lot of votes, but Eric's zenburn
emulation makes my eyes happy. If Jason wins out, I suppose I could
always just read Worg in emacs... :D
>>>
>>> Or use E
On Tue, Jan 18, 2011 at 11:13 AM, Eric Schulte wrote:
> Is there a consensus on removing Javascript folding from *all* pages on
> Worg. I think this would be an improvement both for the readability and
> stylistic coherence of the site.
+1 from me. Also, is the custom worg search box well-liked
"Eric Schulte" writes:
>>>
>>> By the way, having the javascript section-folding enabled on only some
>>> pages is confusing and doesn't make for the best browsing experience.
>>> Now that the TOC will be collapsed by default, perhaps it's no longer
>>> needed?
>>>
>>
>> Yes the javascript is pro
On Tue, Jan 18, 2011 at 3:39 AM, Bastien wrote:
> Jeff Horn writes:
>
>> Jason seems to be garnering a lot of votes, but Eric's zenburn
>> emulation makes my eyes happy. If Jason wins out, I suppose I could
>> always just read Worg in emacs... :D
>
> Or use Eric zenburn-like css by selecting it a
>>
>> By the way, having the javascript section-folding enabled on only some
>> pages is confusing and doesn't make for the best browsing experience.
>> Now that the TOC will be collapsed by default, perhaps it's no longer
>> needed?
>>
>
> Yes the javascript is probably the culprit here, I agree t
Matt Lundin writes:
> Bastien writes:
>
>> Jeff Horn writes:
>>
>>> Jason seems to be garnering a lot of votes, but Eric's zenburn
>>> emulation makes my eyes happy. If Jason wins out, I suppose I could
>>> always just read Worg in emacs... :D
>>
>> Or use Eric zenburn-like css by selecting it
>
> One last change I would suggest, is that rather than use inline css for
> the highlighted source code, we use a css stylesheet by setting the
>
> (setq org-export-htmlize-output-type 'css)
>
> Then use a single .css style sheet as done with the "@import(emacs.css)"
> in my previous submissio
Jason Dunsmore wrote:
> The front page doesn't have a TOC. You can see it here:
> http://orgmode.org/tmp/worg/org-dependencies.html
>
OK - I can see it on this page.
Thanks,
Nick
___
Emacs-orgmode mailing list
Please use `Reply All' to send replie
"Eric Schulte" writes:
> I'm partial to the emacs.css bundled with my
> submission over the current code fontification, but that's just me.
I put your "pre" style in place:
http://orgmode.org/tmp/worg.css
___
Emacs-orgmode mailing list
Please use `Rep
Nick Dokos writes:
> Jason Dunsmore wrote:
>
>> ...
>> That's okay with me. I just uploaded the latest stylesheet with Eric's
>> collapsed TOC integrated in:
>> http://orgmode.org/tmp/worg.css
>>
>> You can see it in action at:
>> http://orgmode.org/tmp/worg/
>>
>
> I haven't been able to see
Jason Dunsmore wrote:
> ...
> That's okay with me. I just uploaded the latest stylesheet with Eric's
> collapsed TOC integrated in:
> http://orgmode.org/tmp/worg.css
>
> You can see it in action at:
> http://orgmode.org/tmp/worg/
>
I haven't been able to see Eric's TOC in action yet (w/Firefo
Bastien writes:
> Thanks all for the work on worg.css -- I'm excited to see this happen!
>
> I'm putting Sebastian explicitely into the loop: I remember Sebastian
> worked on org.css (and maybe worg.css?) to make sure the spacing between
> HTML headings was okay for folding/unfolding through org-
Matt Lundin writes:
> Bastien writes:
>
>> Jeff Horn writes:
>>
>>> Jason seems to be garnering a lot of votes, but Eric's zenburn
>>> emulation makes my eyes happy. If Jason wins out, I suppose I could
>>> always just read Worg in emacs... :D
>>
>> Or use Eric zenburn-like css by selecting it
Bastien writes:
> Jeff Horn writes:
>
>> Jason seems to be garnering a lot of votes, but Eric's zenburn
>> emulation makes my eyes happy. If Jason wins out, I suppose I could
>> always just read Worg in emacs... :D
>
> Or use Eric zenburn-like css by selecting it as an alternative
> stylesheet i
Bastien writes:
> Jeff Horn writes:
>
>> Jason seems to be garnering a lot of votes, but Eric's zenburn
>> emulation makes my eyes happy. If Jason wins out, I suppose I could
>> always just read Worg in emacs... :D
>
> Or use Eric zenburn-like css by selecting it as an alternative
> stylesheet i
Thanks all for the work on worg.css -- I'm excited to see this happen!
I'm putting Sebastian explicitely into the loop: I remember Sebastian
worked on org.css (and maybe worg.css?) to make sure the spacing between
HTML headings was okay for folding/unfolding through org-info-js. Maybe
this is som
Jeff Horn writes:
> Jason seems to be garnering a lot of votes, but Eric's zenburn
> emulation makes my eyes happy. If Jason wins out, I suppose I could
> always just read Worg in emacs... :D
Or use Eric zenburn-like css by selecting it as an alternative
stylesheet in Firefox : View -> Page Styl
Jason seems to be garnering a lot of votes, but Eric's zenburn
emulation makes my eyes happy. If Jason wins out, I suppose I could
always just read Worg in emacs... :D
On Mon, Jan 17, 2011 at 8:34 PM, Matt Lundin wrote:
> Bastien writes:
>
>> Jason Dunsmore writes:
>>
>>> Option 1: http://orgmo
>
> An aside: I noticed that both stylesheets contain a lot of instructions
> that seem to have been created by htmlize.el:
>
That is certainly true of the sheets I submitted, although all of the
htmlize generated css is contained in the separate emacs.css and
zenburn-emacs.css sheets imported by
Bastien writes:
> Jason Dunsmore writes:
>
>> Option 1: http://orgmode.org/tmp/worg-jason/
>> Option 2: http://orgmode.org/tmp/worg-eric/
>> Option 3: http://orgmode.org/tmp/worg-eric2/
>
> Wow! I love this. My preference goes to Jason's version: both plain
> simple and colorful. I also love
Achim Gratz writes:
> Jason Dunsmore writes:
>> I've taken all of your advice to heart and created this improved CSS
>> file:
>>
>> http://orgmode.org/tmp/worg-improved.css
>>
>> :) Joking aside, please send me a patch or CSS file with your
>> suggestions implemented.
>
> I will take a look tomo
Jason Dunsmore writes:
> I've taken all of your advice to heart and created this improved CSS
> file:
>
> http://orgmode.org/tmp/worg-improved.css
>
> :) Joking aside, please send me a patch or CSS file with your
> suggestions implemented.
I will take a look tomorrow, can't promise to do a patch
Achim Gratz writes:
> Jason Dunsmore writes:
>> I made several unit changes from px to em, removed the line-height
>> property, and removed Georgia as the default font:
>
> Well actually, relative font sizing works would be 'larger' and
> 'smaller', which would take into account what fonts are a
Jason Dunsmore writes:
> I made several unit changes from px to em, removed the line-height
> property, and removed Georgia as the default font:
Well actually, relative font sizing works would be 'larger' and
'smaller', which would take into account what fonts are actually
available. Specifying
Hi Jason,
Jason Dunsmore writes:
> "Eric Schulte" writes:
>
>> I recall a discussion of holding a competition to select a new css style
>> for Worg (found it here [1]). I think that such a change could
>> fruitfully be combined with the Worg re-organization.
>
> I'm not a web-designer, but her
>
> Let me know if this still looks good.
>
This looks great to me. The attached version integrates my hidden TOC
style sheet, and I think the TOC looks much better with your headline
styles applied.
The attached worg.css also removes the "line-height:16px;" directive, as
this causes multi-line
Achim Gratz writes:
> Bastien writes:
>> Wow! I love this. My preference goes to Jason's version: both plain
>> simple and colorful.
>
> Please do not use fixed measures in pixels, points, inches or
> centimeters and prescribed font families. Let this choice reside with
> the user, they know
Achim Gratz writes:
> Bastien writes:
>> Wow! I love this. My preference goes to Jason's version: both plain
>> simple and colorful.
>
> Please do not use fixed measures in pixels, points, inches or
> centimeters and prescribed font families. Let this choice reside with
> the user, they know
Bastien writes:
> Wow! I love this. My preference goes to Jason's version: both plain
> simple and colorful.
Please do not use fixed measures in pixels, points, inches or
centimeters and prescribed font families. Let this choice reside with
the user, they know what fonts in which sizes are rea
>>
>> My suggestion would be to go with Jason's css (combined with Eric's
>> expandable table of contents) then have Eric's css and the old-worg
>> css available as alternative css.
>
Sounds good, I like the idea of combining the two styles. I don't know
how alternate css stylesheets work, but I
I like Jason's -- with a non-white bg (text should still be black).
Seems to work with large fonts.
--
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
I support WPI: http://www.wpinstitute.org/xmrv/index.html -- PLEASE DONATE
===
I want to see the original (pre-hold) Lo et al. 2010 NIH/F
Jason the design is superb.
On 2011-01-16, Jason Dunsmore wrote:
> I'm not a web-designer, but here's my stab at re-designing Worg:
> http://orgmode.org/tmp/worg/
--
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
I support WPI: http://www.wpinstitute.org/xmrv/index.html -- PLEASE DONA
Bastien writes:
> Jason Dunsmore writes:
>
>> I updated your first one and added your second one. I also updated mine
>> to use your idea for the Org mascot.
>>
>> So we have three options:
>>
>> Option 1: http://orgmode.org/tmp/worg-jason/
>> Option 2: http://orgmode.org/tmp/worg-eric/
>> Opti
Jason Dunsmore writes:
> I updated your first one and added your second one. I also updated mine
> to use your idea for the Org mascot.
>
> So we have three options:
>
> Option 1: http://orgmode.org/tmp/worg-jason/
> Option 2: http://orgmode.org/tmp/worg-eric/
> Option 3: http://orgmode.org/tmp/
I updated your first one and added your second one. I also updated mine
to use your idea for the Org mascot.
So we have three options:
Option 1: http://orgmode.org/tmp/worg-jason/
Option 2: http://orgmode.org/tmp/worg-eric/
Option 3: http://orgmode.org/tmp/worg-eric2/
I think they're all a majo
1 - 100 of 110 matches
Mail list logo
