Ok, I see, Just I have to replace all uppercased babels and example blocks
to lowercase to keep same.
I have a lot of org files. Huge for me.
I can take with the lower-case tag.
[stardiviner] GPG key ID: 47C32433
IRC(freeenode): stardiviner Twitter: @numbchild
Hello,
Kaushal Modi writes:
> Again it's a font-locking bug, and thankfully doesn't impact the empasis
> detection in exporters.
>
> Would you please look into fixing this?
I cannot. Fixing it would require to rewrite the whole thing to use the
parser, so that fontification matches the syntax o
But how long will we wait for Emacs 26?
On 11/17/2017 03:30 PM, Nicolas Goaziou wrote:
Hello,
Tom Schutter writes:
If both linum-mode (or nlinum-mode) and org-indent-mode are enabled,
then moving the cursor to the previous line using causes it to
jump horizontally to the right. The jump ma
Hello,
Jens Lechtenboerger writes:
> On 2017-11-17, Rasmus wrote:
>
>> Jens Lechtenboerger writes:
>>
>>> the attached patch adds a subtitle macro with documentation.
>>
>> AFAIK it’s already added to the backends where it makes sense. It’s not a
>> basic keyword like "#+author". It should be
Hello,
Tom Schutter writes:
> If both linum-mode (or nlinum-mode) and org-indent-mode are enabled,
> then moving the cursor to the previous line using causes it to
> jump horizontally to the right. The jump matches the current
> indentation. I would expect the cursor to remain in the same col
Hello,
Umbromancer writes:
> This may be intended, but before it was possible (and there is a lot
> of code and examples in the wild) to have a capture template element
> such as:
I don't see this documented either in `org-capture-templates' docstring
or in the manual. It could be some glitch t
Hello,
Doro Rose writes:
> In summary, yes I'm accessing user settings but in a rather
> noninvasive way. Unfortunately I can't think of a more elegant way to
> do this.
Let's put it differently then. Isn't it the job of the user, who changed
their prompt, to configure properly "inf-haskell" li
Hello,
Akater writes:
> In case UNNUMBERED's inheritance could be turned off by a standard
> procedure, my other points are meaningless. So let's first figure out if
> it could.
It cannot. That's a feature intended to preserve sanity.
As suggested, you could write an export back-end that ignor
"numbch...@gmail.com" writes:
> Yeah, I misunderstand your code. Anyway, It should be like this:
>
> #+BEGIN_SRC python
> ...
> #+END_SRC
>
> #+BEGIN_EXAMPLE
> ...
> #+END_EXAMPLE
>
> etc
If you look back up this (admittedly very long) thread, you'll see the
general consensus is to move to lower
Yeah, I misunderstand your code. Anyway, It should be like this:
#+BEGIN_SRC python
...
#+END_SRC
#+BEGIN_EXAMPLE
...
#+END_EXAMPLE
etc
[stardiviner] GPG key ID: 47C32433
IRC(freeenode): stardiviner Twitter: @numbchild
Key fingerprint = 9BAA 92BC CDDD B9EF 3
I setted `haskell-process-type` to 'ghci.
I evaluated a simple haskell src block, but it reports I need have a
`*haskell*` inferior. Then I executed command [M-x run-haskell].
Then I get error:
Debugger entered--Lisp error: (wrong-type-argument stringp nil)
expand-file-name(nil)
locate-dominat
Kaushal Modi writes:
> Have you looked at org-use-property-inheritance variable
> http://orgmode.org/manual/Property-inheritance.html -- You can set that to
> a regexp that does not match UNNUMBERED.
As this page mentions, default value is nil, which means nothing would be
inherited. UNNUMBERED
On Fri, Nov 17, 2017, 7:00 AM Akater wrote:
> I have to deal with a document that has an unfortunate vague structure
> which involves unnumbered headlines spanning a couple of numbered
> ones. I'd like to convert the document into Org and thus effectively
> need to implement a feature that would
I have to deal with a document that has an unfortunate vague structure
which involves unnumbered headlines spanning a couple of numbered
ones. I'd like to convert the document into Org and thus effectively
need to implement a feature that would allow unnumbered property in Org
not to be inherited b
On Fri, Nov 17, 2017, 4:35 AM Alan Schmitt
wrote:
>
> It makes sense. Reading the text there, I'm a bit surprised:
>
> For example, `DATE' and `EXPORT_FILE_NAME' keywords become,
> respectively, `EXPORT_DATE' and `EXPORT_FILE_NAME'.
>
> Is the `EXPORT_FILE_NAME' a real example (i.e., a node prope
On 2017-11-16 22:00, Nicolas Goaziou writes:
> Alan Schmitt writes:
>
>> The LaTeX header and sectioning structure info node talks about
>> LATEX_HEADER and LATEX_HEADER_EXTRA. Maybe it could mention the EXPORT
>> version as well, as is done for the LATEX_CLASS_OPTION.
>
> Since adding "EXPORT_"
Dear David,
> "David" == David Arroyo Menendez writes:
David> I would like share my public agenda and read public agendas
David> of another worgers, perhaps we can share our agendas in a git
David> repository, or from different sources linked from
David> worgers.org. Are there
On 2017-11-17, Rasmus wrote:
> Jens Lechtenboerger writes:
>
>> the attached patch adds a subtitle macro with documentation.
>
> AFAIK it’s already added to the backends where it makes sense. It’s not a
> basic keyword like "#+author". It should be documented under the relevant
> backends that
18 matches
Mail list logo
