* lisp/ox-html.el (org-html-style-default): `.done' gets `font-family:
monospace;'
Other items on the headline that aren't the text itself are monospaced,
including non-DONE todo's.
TINYCHANGE
---
lisp/ox-html.el | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lisp/ox-html.el
* list/ox-html.el (org-html--priority): new function
(org-html-format-headline-default-function): call `org-html--priority'
(org-html-style-default): add `.priority'
HTML export previously did not support exporting of priority simply by setting
`org-export-with-priority' to `t'.
TINYCHANGE
---
l
Could someone please chime in on this?
On Sunday, January 4, 2015, Yuri Niyazov wrote:
> Let's say I start with a .notes file that looks like this:
>
> #+BEGIN_EXAMPLE
> * Tasks
> * Refile Here
> * Other Stuff
> #+END_EXAMPLE
>
> with all the default capture templates.
>
> The only org-mode conf
Nice!
I spent some time figuring out how to use it.
This is what I did eventually:
M-xlentic-mode
M-xlentic-mode ;; twice
M-x lentic-mode-split-window-below
Then change the new buffer to the desired mode (Java mode, C++ mode,
whatever).
(I was created in fundamental mode).
Is this the st
I thought some of you might be interested in the new release of my
package, lentic. One of the things that it now does is allow
multi-modal of editing of Emacs source, using org mode for the
documentation. I realise that it's already possible to use ELPA
org-babel to write literate el files, or t
I'm no lisp expert, but I have attempted to indent the backtrace below for
easier reading.
Debugger entered--Lisp error:
(error "Capture abort: (wrong-type-argument stringp
(file:~/org/todo.org::*Tasks Tasks))")
signal(error ("Capture abort: (wrong-type-argument stringp
(file:~/org/todo.org::*T
On Thursday, 8 Jan 2015 at 21:04, Sebastien Vauban wrote:
> You're right; it isn't.
And reading the page again, it is entitled "Typesetting conventions used
in this manual" so it's more about writing a manual than about what org
supports!
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.1, Org
rel
Eric S Fraga wrote:
> On Wednesday, 7 Jan 2015 at 22:24, Sebastien Vauban wrote:
>
> [...]
>
>> "User-defined properties are capitalized", see
>> http://orgmode.org/manual/Conventions.html.
>
> A convention is not a requirement, is it? I hate typing upper case
> letters...
You're right; it isn't
On Wednesday, 7 Jan 2015 at 22:24, Sebastien Vauban wrote:
[...]
> "User-defined properties are capitalized", see
> http://orgmode.org/manual/Conventions.html.
A convention is not a requirement, is it? I hate typing upper case
letters...
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.1, Org
r
I am trying to use the following keyboard test macro
(fset 'jj [?\C-c ?c ?t ?j ?j return ?\C-c ?\C-c])
to invoke this capture template definition
(setq org-capture-templates '(("t" "Todo" entry (file "~/org/j.org"
Note that C-c c invokes M-x org-capture.
Unfortunately, it produce
> > The backtrace is not very useful as is because of the byte code. You
> > might try to reproduce with uncompiled code and see if it is any
> > clearer.
>
> How to do that? I had used
> C-u M-x org-reload RET
> before, as described in the org-mode documentation to get a backtrace from
> unco
Michael Brand writes:
> Hi Wim
>
> On Wed, Jan 7, 2015 at 6:11 PM, Willem Rein Oudshoorn
> wrote:
>> ...
>> However org mode table formula code seems to strip the display property
>> from the string returned by the formula. So this trick will not work.
>
> I think this is by design. If someone
Hi Wim
On Wed, Jan 7, 2015 at 6:11 PM, Willem Rein Oudshoorn
wrote:
> I am trying to insert an image into a table by using a table formula.
> My basic approach is by using a string with a display property like:
>
>
> (propertize "TEXT" 'display (list image))
>
>
> Or to be more precise
>
>(
Nicolas Goaziou writes:
> Hello,
>
> Giuseppe Lipari writes:
>
>> As a matter of fact, I think the :width option for latex tables should be
>> disabled, because it is not so simple to implement.
>
> As long as it doesn't generate invalid LaTeX code (like in your bug
> report), I think the current
Hello,
Giuseppe Lipari writes:
> As a matter of fact, I think the :width option for latex tables should be
> disabled, because it is not so simple to implement.
As long as it doesn't generate invalid LaTeX code (like in your bug
report), I think the current :width option can be kept. You don't
On Thu, Jan 08, 2015 at 10:34:44AM +0100, Rasmus wrote:
> Peter Davis writes:
>
> > Is there any way to completely redact text in HTML export, so it just
> > looks like black boxes?
>
> I'm not sure I fully understand, but it this what you are looking for?
>
> #+MACRO: redact @@html:$1@@
> to {
On 2015-01-08 10:17, Myles English writes:
> Hello,
>
> Can anybody tell me how this could be achieved, please?
>
> I would like to use parameters for ledger[1] source code blocks, and
> understand that the :cmdline header argument means "pass this straight
> through to the command line", but eff
Hello,
Can anybody tell me how this could be achieved, please?
I would like to use parameters for ledger[1] source code blocks, and
understand that the :cmdline header argument means "pass this straight
through to the command line", but effectively what I would like to do is
this:
#+PROPERTY: he
Peter Davis writes:
> Is there any way to completely redact text in HTML export, so it just
> looks like black boxes?
I'm not sure I fully understand, but it this what you are looking for?
#+MACRO: redact @@html:$1@@
to {{{redact(redact)}}} or not to {{{redact(redact)}}} that is the question.
Hi,
thanks for responding.
As a matter of fact, I think the :width option for latex tables should be
disabled, because it is not so simple to implement.
While it is possible to reduce the width with Eric's trick, it is not so
easy to enlarge the width without using the :align option and appropriat
20 matches
Mail list logo
