Eric S Fraga e.fr...@ucl.ac.uk writes:
Indeed. Attached is a very simple patch to fix these missing
s. Untested.
Applied, thanks a lot!
--
Bastien
Bernt Hansen be...@norang.ca writes:
Eric S Fraga e.fr...@ucl.ac.uk writes:
Bernt Hansen be...@norang.ca writes:
[...]
I added the following to my .emacs to keep lowercase.
Thanks. This is a great suggestion! Two possible typos, by the way,
that would only affect you if you use muse
Bernt Hansen be...@norang.ca writes:
[...]
I added the following to my .emacs to keep lowercase.
Thanks. This is a great suggestion! Two possible typos, by the way,
that would only affect you if you use muse tags:
(v #+begin_verse\n?\n#+end_verse verse\n?\n/verse)
Eric S Fraga e.fr...@ucl.ac.uk writes:
Bernt Hansen be...@norang.ca writes:
[...]
I added the following to my .emacs to keep lowercase.
Thanks. This is a great suggestion! Two possible typos, by the way,
that would only affect you if you use muse tags:
(v
A long time ago all capitals was the only way these keywords were
supported. Since then they have become case insensitive and I use all
lowercase for most of my keywords now (#+begin_src:, #+begin_example:
etc)
With fontification these stand out enough now and the capitalization can
be
Sebastien Vauban writes:
François Pinard wrote:
Bastien writes:
Eric Schulte writes:
Could the highlighting be made consistent as well? I would suggest that
gray is uniformly kept for all one-line option/environment keywords.
Currently, #+TITLE is gray, #+OPTIONS is red, so #+OPTION would
Bastien b...@altern.org writes:
Hi François,
Could the highlighting be made consistent as well?
As Sébastien suggested, please contribute to this page:
http://orgmode.org/worg/color-themes-screenshot.html
Hello, Bastien. I hope you'll forgive me if I decline this invitation.
My suggestion
Hi François,
François Pinard wrote:
Sebastien Vauban writes:
François, Are you talking of a dark theme or light theme?
I do not know, as I do not use themes. The background is white, if this is
what you mean.
Yep, that's what I meant.
So, I'm merely speaking about Org mode defaults. My
Bastien b...@altern.org writes:
Actually, I'm thinking of another solution:
- keep one-line option/environment keywords uppercase
#+NAME
#+HTML
#+TITLE
#+...
- use lowercase for multi-lines environments keywords
#+begin_ascii
#+begin_html
#+results
This is the only
Hi François,
pin...@iro.umontreal.ca (François Pinard) writes:
Could the highlighting be made consistent as well? I would suggest that
gray is uniformly kept for all one-line option/environment keywords.
Currently, #+TITLE is gray, #+OPTIONS is red, so #+OPTION would be
rendered the same as
Bastien b...@altern.org writes:
Bastien b...@altern.org writes:
Actually, I'm thinking of another solution:
- keep one-line option/environment keywords uppercase
#+NAME
#+HTML
#+TITLE
#+...
- use lowercase for multi-lines environments keywords
#+begin_ascii
#+begin_html
I'm going to push up a patch which will change to inserting #+RESULTS:
by default as well as a user-configurable variable which can be used to
customize this behavior.
Done. This variable is named `org-babel-results-keyword'
,
| org-babel-results-keyword's value is RESULTS
|
|
Eric Schulte eric.schu...@gmx.com writes:
I'm going to push up a patch which will change to inserting #+RESULTS:
by default as well as a user-configurable variable which can be used to
customize this behavior.
Done. This variable is named `org-babel-results-keyword'
Great, thanks. I've
Nick Dokos nicholas.do...@hp.com writes:
François Pinard pin...@iro.umontreal.ca wrote:
P.P.S. How about amending the manual for consistent capitalization?
Knock yourself out! ;-)
I've absolutely nothing against doing that little work myself (that one
is easy enough!), besides the idea
François Pinard pin...@iro.umontreal.ca wrote:
Nick Dokos nicholas.do...@hp.com writes:
François Pinard pin...@iro.umontreal.ca wrote:
P.P.S. How about amending the manual for consistent capitalization?
Knock yourself out! ;-)
I've absolutely nothing against doing that little
Hey François,
bh I wouldn't spend too much time agonizing over the 'right' way
fp Truth is that I've been so agonizing for the whole of my computer
fp life! Each one his sickness, I guess... :-)
I understand your pain. Have you read The Paradox of Choice by Bary
Schwartz? Sounds as if you
Hi François,
pin...@iro.umontreal.ca (François Pinard) writes:
P.P.S. How about amending the manual for consistent capitalization?
I've pushed a fix for this.
The manual used mostly uppercase so I fixed the few lowercase
instances of option/environment keywords.
I made an exception for
Bastien b...@altern.org writes:
Hi François,
pin...@iro.umontreal.ca (François Pinard) writes:
P.P.S. How about amending the manual for consistent capitalization?
I've pushed a fix for this.
The manual used mostly uppercase so I fixed the few lowercase
instances of option/environment
Eric Schulte eric.schu...@gmx.com writes:
That said I'm happy that Org-mode is forgiving enough to allow me to
lowercase most of my keywords locally.
Actually, I'm thinking of another solution:
- keep one-line option/environment keywords uppercase
#+NAME
#+HTML
#+TITLE
#+...
- use
Bastien b...@altern.org writes:
Eric Schulte eric.schu...@gmx.com writes:
That said I'm happy that Org-mode is forgiving enough to allow me to
lowercase most of my keywords locally.
Actually, I'm thinking of another solution:
- keep one-line option/environment keywords uppercase
#+NAME
pin...@iro.umontreal.ca (François Pinard) writes:
Bastien b...@altern.org writes:
Eric Schulte eric.schu...@gmx.com writes:
That said I'm happy that Org-mode is forgiving enough to allow me to
lowercase most of my keywords locally.
Actually, I'm thinking of another solution:
- keep
pin...@iro.umontreal.ca (François Pinard) writes:
Hi, Org people.
I really have mixed feelings about capitalisation of #+WORDS, and wonder
if some consensus and good taste has developed over time among Org mode
users. What is the collective wisdom saying as being nicer among:
[...]
Maybe
pin...@iro.umontreal.ca (François Pinard) writes:
[...]
Should I say, I notice a strong correlation between rotten software and
the lack of attention to such details. I'm not saying that avoiding
trailing white space is a guarantee of good software. But I'm saying
that people unwilling to
2012/1/11 Eric S Fraga e.fr...@ucl.ac.uk
pin...@iro.umontreal.ca (François Pinard) writes:
[...]
Should I say, I notice a strong correlation between rotten software and
the lack of attention to such details. I'm not saying that avoiding
trailing white space is a guarantee of good
Hi Bastien,
François Pinard wrote:
Bastien b...@altern.org writes:
Eric Schulte eric.schu...@gmx.com writes:
That said I'm happy that Org-mode is forgiving enough to allow me to
lowercase most of my keywords locally.
Actually, I'm thinking of another solution:
- keep one-line
Hi, Org people.
I really have mixed feelings about capitalisation of #+WORDS, and wonder
if some consensus and good taste has developed over time among Org mode
users. What is the collective wisdom saying as being nicer among:
#+LATEX_HEADER:
#+Latex_Header:
#+LaTeX_HEADER:
#+latex_header:
pin...@iro.umontreal.ca (François Pinard) writes:
I really have mixed feelings about capitalisation of #+WORDS, and wonder
if some consensus and good taste has developed over time among Org mode
users. What is the collective wisdom saying as being nicer among:
#+LATEX_HEADER:
Bernt Hansen be...@norang.ca wrote:
pin...@iro.umontreal.ca (François Pinard) writes:
I really have mixed feelings about capitalisation of #+WORDS, and wonder
if some consensus and good taste has developed over time among Org mode
users. What is the collective wisdom saying as being
Bernt Hansen be...@norang.ca writes:
pin...@iro.umontreal.ca (François Pinard) writes:
I really have mixed feelings about capitalisation of #+WORDS, and
wonder if some consensus and good taste has developed over time among
Org mode users.
A long time ago all capitals was the only way these
Nick Dokos nicholas.do...@hp.com writes:
... and check out easy templates to get consistent capitalization
*and* speed up your typing: (info (org) Easy Templates)
Good advice! Thanks!
François
P.S. By the way, the node mentions #+begin_ascii, but the manual does
not tell about what it is.
François Pinard pin...@iro.umontreal.ca wrote:
P.S. By the way, the node mentions #+begin_ascii, but the manual does
not tell about what it is. (Or at least t s begin_ascii RET s RET in
the Info node only finds the Easy Templates reference.)
In general, #+begin_foo ... #+end_foo will
31 matches
Mail list logo
