Hi,
Brady Trainor writes:
> Ilya Shlyakhter writes:
>
>> dear org-moders,
>> is it possible to syntax-highlight inline LaTeX fragments,
>> such as $V$ or \cite{smith2012generating} ?
>> I know you can highlight LaTeX code blocks, but I'm looking
>> specifically for highlighting of inline fragme
Nicolas Goaziou writes:
> I cannot reproduce it. Publishing "global" project succeeds.
Did you publish asynchronously ? I can publish "global" and "latex"
synchronously, "latex" asynchronously (see the following *Org Export
Process* buffer) : only "global" fails when run asynchronously.
--8<---
Kyle Meyer wrote:
> Nicolas Goaziou wrote:
> [...]
>> However, C-m is RET. Is there any reason to distinguish between the two?
>
> If I use just
>
> (define-key org-goto-local-auto-isearch-map [return] nil)
>
> then C-m doesn't work (i.e., it results in isearch-exit being called
> instead of
Ilya Shlyakhter writes:
> dear org-moders,
> is it possible to syntax-highlight inline LaTeX fragments,
> such as $V$ or \cite{smith2012generating} ?
> I know you can highlight LaTeX code blocks, but I'm looking
> specifically for highlighting of inline fragments.
> thanks for help,
> ilya
:bump
Hi Grant,
This is exactly the behavior I get too.
Thank you for documenting it precisely.
Let me clarify one step:
“put the cursor on line 2 in ex1.js, _and modify that line_, and
then call org-babel-detangle”
And no, I don’t think what happens is the expected behavior.
I would expect the con
Hello,
just wondering: on one hand, we have lines like
#+OPTIONS: toc:nil
On the other hand, we have
#+ATTR_ASCII: :width 10
Why is the syntax (seemingly, at least) inconsistent? Why not
`width:10' or `:toc nil'?
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam
On Sat, Nov 1, 2014 at 5:58 AM, Thorsten Jolitz wrote:
> And there is a new library
>
> [[http://goo.gl/pYYzS6][outorg-export]]
I just used http://goo.gl/pYYzS6 and it worked fine; that looks like
an org mode link.
On 2014-11-03 at 01:23, Rasmus wrote:
> Hello,
>
> "Garreau, Alexandre" writes:
>> On 2014-11-02 at 22:48, John Kitchin wrote:
>>> Nicolas Goaziou writes:
>>> Interestingly, this:
>>> #+LATEX_HEADER: \usepackage{chemfig}
>>> $\chemfig{A-B-[1]C-[3]-D-[7]E-[6]F}$
>>> exports to pdf correctly, but t
Good evening,
1 Attempt
═
Just tried out your example. So it is crystal clear, I did use the
following:
1.1 Source input: ex1.org
─
┌
│ * Heading
│
│ #+BEGIN_SRC js :comments noweb :tangle yes :padline no
│ function foo() {}
│ #+END_SRC
Hello,
g"Garreau, Alexandre" writes:
> On 2014-11-02 at 22:48, John Kitchin wrote:
>> Nicolas Goaziou writes:
>> Interestingly, this:
>> #+LATEX_HEADER: \usepackage{chemfig}
>> $\chemfig{A-B-[1]C-[3]-D-[7]E-[6]F}$
>> exports to pdf correctly, but the latex preview is not correct. All the
>> let
On 2014-11-02 at 22:48, John Kitchin wrote:
> Nicolas Goaziou writes:
>
> Interestingly, this:
>
> #+LATEX_HEADER: \usepackage{chemfig}
>
>
> $\chemfig{A-B-[1]C-[3]-D-[7]E-[6]F}$
>
>
> exports to pdf correctly, but the latex preview is not correct. All the
> letters are jumbled on top of each othe
Nicolas Goaziou wrote:
[...]
> However, C-m is RET. Is there any reason to distinguish between the two?
If I use just
(define-key org-goto-local-auto-isearch-map [return] nil)
then C-m doesn't work (i.e., it results in isearch-exit being called
instead of org-goto-ret, then requiring a seco
Kyle Meyer writes:
> Hmm, I tried that (and just checked it again), but it doesn't work on my
> end. C-m will exit isearch but not the indirect org-goto buffer. A
> second C-m is needed to get back to the main buffer. (This is also true
> for return, which is why it is also set to nil.) For C-i,
John Hendy writes:
> Thanks for the explanation. I pretty much only use duration, which has
> never had an issue. As a fluke I used effort and noticed the big
> difference. Thanks for illuminating the situation!
Actually, I was slightly wrong. According to
`org-duration-string-to-minutes' and `o
On Sun, Nov 2, 2014 at 5:01 PM, Nicolas Goaziou wrote:
> John Hendy writes:
>
>> That mostly makes sense. Org's not case-sensitive, correct?
>
> Correct.
>
>> I was looking at the [granted, outdated] taskjuggler documentation and
>> it features estimates in days (i.e. 10d): -
>> http://orgmode.or
John Hendy writes:
> That mostly makes sense. Org's not case-sensitive, correct?
Correct.
> I was looking at the [granted, outdated] taskjuggler documentation and
> it features estimates in days (i.e. 10d): -
> http://orgmode.org/worg/org-tutorials/org-taskjuggler.html
>
> Is this recent (as in
On Sun, Nov 2, 2014 at 4:55 PM, Nicolas Goaziou wrote:
> Hello,
>
> John Hendy writes:
>
>> It's up to someone else regarding whether or not the #+property
>> behavior is desired. I wondered what two subsequent #+options lines
>> would do, for example, and they appear to be cumulative. For exampl
On Sun, Nov 2, 2014 at 4:47 PM, Nicolas Goaziou wrote:
> Hello,
>
> John Hendy writes:
>
>> I ran into an error with a 30min task which used the :effort: property
>> to set this duration. Upon compilation, I noted the warning:
>> ```
>> file.tjp:10: Warning: 400.0d of effort of task one does not
Hello,
John Hendy writes:
> It's up to someone else regarding whether or not the #+property
> behavior is desired. I wondered what two subsequent #+options lines
> would do, for example, and they appear to be cumulative. For example:
>
> #+options: toc:nil
> #+options: num:nil
>
> Yielded both
On Fri, Oct 31, 2014 at 11:50 PM, myq larson wrote:
> Remember to cover the basics, that is, what you expected to happen and
> what in fact did happen. You don't know how to make a good report? See
>
> http://orgmode.org/manual/Feedback.html#Feedback
>
> Your bug report will be posted to th
Hello,
John Hendy writes:
> I ran into an error with a 30min task which used the :effort: property
> to set this duration. Upon compilation, I noted the warning:
> ```
> file.tjp:10: Warning: 400.0d of effort of task one does not fit into
> the project time frame.
> Warning: 1 tasks could not be
Nicolas Goaziou wrote:
[...]
> C-i and C-m seem to work out the box in Emacs 24.4 anyway. Maybe the
> following is sufficient:
>
> (when (fboundp 'isearch-other-control-char)
> (define-key ...)
> (define-key ...))
>
> I.e, no need to bind these keys to nil.
Hmm, I tried that (and just c
Hello,
Julien Cubizolles writes:
> In git master, consider the following,
>
> #+begin_src emacs-lisp :tangle yes :exports none
> (setq org-publish-project-alist
> `(("latex"
>:base-directory "./"
>:publishing-directory "./"
>:publishing-function org-
I ran into an error with a 30min task which used the :effort: property
to set this duration. Upon compilation, I noted the warning:
```
file.tjp:10: Warning: 400.0d of effort of task one does not fit into
the project time frame.
Warning: 1 tasks could not be scheduled
```
I looked at the .tjp file
Hello,
Kyle Meyer writes:
> As of Emacs 24.4, isearch no longer has the function
> isearch-other-control-char, which is bound in
> org-goto-local-auto-isearch-map.
>
> I've attached a patch that seems to produce the correct behavior with
> Emacs 24.4. However, I haven't used this interface enoug
Hello,
Jan Synacek writes:
> I'm not sure if this is by design or not, but it sure looks like a bug
> to me and is quite annoying.
>
> Reproducer:
> 1) emacs -Q
> 2) eval the following:
> (require 'org)
> (setq org-log-done 'time)
> (setq org-log-into-drawer t)
> (setq org-todo-keywords
>
Hello,
"Charles C. Berry" writes:
> The attached patch enables this by adding a blank line after a
> `paragraph', but before a `plain-list' as long as the `paragraph' is not
> itself inside a list.
Thanks for your patch. I applied a different one, though.
I find blank lines rules in Markdow
Edit: sorry about the premature send. Bad accidental tab + enter from
gmail! Here's the intended email:
===
I note that the defaults for a taskjuggler export in Org are as
follows, with taskjuggler syntax and related org variable definitions
listed.
Project tj syntax: project [] [] [{
}]
Org
I note that the defaults for a taskjuggler export in Org are as
follows, with taskjuggler syntax and related org variable definitions
listed.
Project tj syntax: project [] [] [{
}]
Org defaults:
- id: nil
- name: name of heading tagged with org-taskjuggler-project-tag
- version: org-taskjugler
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
--
I am not a committer. Previously I've always sent in new versions of
org-velocity as patches, following the procedure on the Org wiki. I don't
usually follow the mailing list, so perhaps the procedure for handling
contributions has changed without my noticing. If so I'm happy to adjust.
Paul Rodri
Hello,
I'm not sure if this is by design or not, but it sure looks like a bug
to me and is quite annoying.
Reproducer:
1) emacs -Q
2) eval the following:
(require 'org)
(setq org-log-done 'time)
(setq org-log-into-drawer t)
(setq org-todo-keywords
'((sequence "TODO(t)" "WAITING(w@/!)" "|" "
I'm afraid I don't understand the question. Is there a problem with the
patch?
Paul Rodriguez.
On Thu, Oct 30, 2014 at 2:18 PM, Marco Wahl wrote:
> Hello Paul,
>
> Paul Rodriguez writes:
>
> > This is a new version of org-velocity. Principally it differs in using
> > cl-lib and lexical bindin
a couple of weeks ago I decided I would use emacs for my spreadsheets. I
first tried with `ses`, then I was pointed at the spreadsheet
capabilities of org-mode. but I also needed to see a graph
representation of the data.
http://stackoverflow.com/questions/26614536/
tables in org-mode work really
Nicolas Goaziou writes:
Interestingly, this:
#+LATEX_HEADER: \usepackage{chemfig}
$\chemfig{A-B-[1]C-[3]-D-[7]E-[6]F}$
exports to pdf correctly, but the latex preview is not correct. All the
letters are jumbled on top of each other.
> "Garreau, Alexandre" writes:
>
>>> Have you tried
>>>
>
John Hendy pointed out [1] that
list
- item1
- item2
Isn't the same as this:
list
- item1
- item2
when exported using the `md' backend (or its derivatives). But it needs to
be to generate a proper document (at least with engines like pandoc.)
The attached patch enables this by adding a bl
Roberto Huelga writes:
> I founded a section in the org-contribute.html with the names of the
> tiny change contributors,
> Do you know how could I get my name there? This is my second
> tinychange patch. And
> get my name in the list will make my day.
Your name is already in that list. You may
In git master, consider the following,
--8<---cut here---start->8---
#+begin_src emacs-lisp :tangle yes :exports none
(setq org-publish-project-alist
`(("latex"
:base-directory "./"
:publishing-directory "./"
:publishin
Hello,
Julien Cubizolles writes:
> The latest org-plus-contrib (20141027) from org/melpa seems to have
> reverted to using \textwidth instead of \columnwidth. Why is that ? The
> master branch from git is ok though (meaning it uses \columnwidth).
org-plus-contrib is stable (maint) branch. The c
"Garreau, Alexandre" writes:
>> Have you tried
>>
>> #+LATEX_HEADER: \usepackage{chemfig}
>
> Yes. I think it doesn’t influence the preview system.
It should. Perhaps your Org is outdated.
Regards,
--
Nicolas Goaziou
Hello,
As of Emacs 24.4, isearch no longer has the function
isearch-other-control-char, which is bound in
org-goto-local-auto-isearch-map.
I've attached a patch that seems to produce the correct behavior with
Emacs 24.4. However, I haven't used this interface enough in the past (I
have org-goto-i
On 2014-10-29 15:34, Robert Horn writes:
> Jay Iyer writes:
>
>> If there are use cases out there, it might be worth collecting them and
>> then thinking about how to support them better. If there aren't, maybe
>> it should be thrown out.
>
> It's most definitely useful. I'm not sure what you th
a couple of weeks ago I decided I would use emacs for my spreadsheets. I
first tried with `ses`, then I was pointed at the spreadsheet
capabilities of org-mode. but I also needed to see a graph
representation of the data.
http://stackoverflow.com/questions/26614536/
tables in org-mode work really
Nicolas Goaziou writes:
> Hello,
>
> Julien Cubizolles writes:
>
>> I don't think there would be any inconvenients to changing \textwidth to
>> \columnwidth for regular beamer files (it's fine with my beamer files so
>> far).
>
> I agree. Done in master. Thank you for suggesting it.
The latest
Le 02/11/2014 à 20h45, Nicolas Goaziou a écrit :
> Hello,
>
> "Garreau, Alexandre" writes:
>
>> Hello, I’d like to being able to preview chemfig, like lines beginning
>> with \chemfig{.
>>
>> But (a) they’re not detected as LaTeX fragments by the previewer (and it
>> seems only some matchers are a
I founded a section in the org-contribute.html with the names of the
tiny change contributors,
Do you know how could I get my name there? This is my second
tinychange patch. And
get my name in the list will make my day.
Thanks
2014-11-02 10:44 GMT+01:00 Nicolas Goaziou :
> Roberto Huelga writes:
On 2014-11-02 18:08 Nicolas Goaziou wrote:
> Hello,
>
> Alexander Baier writes:
>
>> I am looking for a function that starts at point and walks up the
>> outline-tree searching for property P. If P is defined the function
>> returns P's value, otherwise nil. If The top level headline does not
>> h
Hello,
"Garreau, Alexandre" writes:
> Hello, I’d like to being able to preview chemfig, like lines beginning
> with \chemfig{.
>
> But (a) they’re not detected as LaTeX fragments by the previewer (and it
> seems only some matchers are accepted by default, I can’t say, for
> instance, “^{\\[a-zA-
Hi Łukasz,
Thanks for the patch.
I tested your package briefly, but I did not look into the code.
Łukasz Gruner writes:
> I would like to contribute Eldoc support.
It works nice for source blocks. However, I don't get any feedback in
header-lines:
#+header:
#+begin_src emacs-lisp
...
#+
Hello, I’d like to being able to preview chemfig, like lines beginning
with \chemfig{.
But (a) they’re not detected as LaTeX fragments by the previewer (and it
seems only some matchers are accepted by default, I can’t say, for
instance, “^{\\[a-zA-Z]*[a-zA-Z0-9 ].*}$”), and (b) when previewing I
d
Hi Lukasz,
Thanks for your contribution.
2014ko azaroak 1an, Łukasz Gruner-ek idatzi zuen:
>
> Hi
>
> I would like to contribute Eldoc support.
> I've already changed license, but dont quite get that pgp part, I have
> generated my pgp and now what?
There’s a couple of issues.
1. Write access
Hello,
Alexander Baier writes:
> I am looking for a function that starts at point and walks up the
> outline-tree searching for property P. If P is defined the function
> returns P's value, otherwise nil. If The top level headline does not
> have a property P, the function looks for #+P between
Hello,
I am looking for a function that starts at point and walks up the
outline-tree searching for property P. If P is defined the function
returns P's value, otherwise nil. If The top level headline does not
have a property P, the function looks for #+P between the first headline
and bob.
Is th
On November 2, 2014 4:25:53 PM Nicolas Goaziou wrote:
Actually, it isn't. This is a feature.
Both `M-S-up' and `M-S-down' work line wise and ignore any structure
around point. OTOH, `M-up' and `M-down' should do what you want.
Ah, OK... It would be a bug if there were no function to move a l
Roberto Huelga writes:
> Suppose you want to write the parent directory name in your capture so write a
> template like
>
> "* %(file-name-nondirectory (directory-file-name (file-name-directory
> \"%F\")))"
>
> Without the patch, file-name-directory get the useless string "%F"
> instead of a str
Hello,
James Harkins writes:
> In plain lists, if there is indented text underneath a list item, is
> it considered to "belong to" the list item, or is it just freestanding
> text?
The former.
> I'm asking because M-S-up/down doesn't take indented text into
> account. These commands only move
Hello,
Kyle Meyer writes:
> A patch for a minor docstring typo is attached.
Applied. Thank you.
Regards,
--
Nicolas Goaziou
In plain lists, if there is indented text underneath a list item, is it
considered to "belong to" the list item, or is it just freestanding text?
I'm asking because M-S-up/down doesn't take indented text into account. These
commands only move the line marked with a list-item indicator ("-" etc.)
58 matches
Mail list logo
