Re: [O] org-ref in action

[Joseph Vidal-Rosset]

Hi John, hello the list,

My question is very simple and it is not unrevelevant vis-à-vis this
thread, therefore I keep  the same thread.

What  need is to get either  the usual citation format  (often in plain
style) \cite{one-reference-paper-year} or this one with a mentioned page:
\cite[page n]{one-reference-paper-year}.

My problem with cite: org-mode format is that I am not able to get the
second format. Ideally , I want to click on the reference and just to add
the quoted page.

I do not doubt that this is easy to get in org-mode, but I'm wasting my
time to find how... if it is possible to get it with org-ref  or via
another tool, many thanks in advance.

Best regards

Jo.
​

[O] [PATCH] curly nested latex fragments (was: superscript not available after non-alphanumeric)

[heroxbd]

Hello Nicolas,

Nicolas Goaziou  writes:

> If you want to insert raw LaTeX in an Org buffer, then \ce{^{238}U} is
> invalid because you cannot nest braces. You can write instead:
>
>   @@latex:\ce{^{238}U}@@
>
> or you can define a macro, e.g.,:
>
>   #+MACRO: ce @@latex:\ce{$1}@@
>
> and then use
>
>   {{{ce(^{238}U)}}}

Nesting braces is already implemented in the classic org-latex.el[1],
and is forward ported into org-element.el.  Would you like to take a
look at the attached patch? Thanks.

> Also, ^2H is not recognized as superscript _on purpose_. Per Org syntax,
> you have to add a non-blank character before the caret. Otherwise, there
> would be ambiguity between underline (e.g., _under_) and subscript
> (_under). And superscript syntax follows subscript's.
>
> In this case, you can probably use a math snippet, e.g.,
>
>   \(^2\)H

If \ce{^2H} works as above, it is not a problem for me.  Although make
it configurable is more user-friendly; "^:{}" is already there afterall,
adding another style feels natural.

Thanks,
Benda

1. 
http://orgmode.org/w/org-mode.git?p=org-mode.git;a=blob;f=lisp/org-latex.el;hb=107f921d121f5a9bb5a9324f19339e4435633d2d#l2597

support nested curly bracket pairs in latex fragments.

http://lists.gnu.org/archive/html/emacs-orgmode/2014-06/msg01022.html

Index: org-8.2.7b/lisp/org-element.el
===
--- org-8.2.7b.orig/lisp/org-element.el
+++ org-8.2.7b/lisp/org-element.el
@@ -3026,7 +3026,12 @@ Assume point is at the beginning of the
    (looking-at latex-regexp
 		(throw 'exit (nth 2 e)
 	  ;; None found: it's a macro.
-	  (looking-at "[a-zA-Z]+\\*?\\(\\(\\[[^][\n{}]*\\]\\)\\|\\({[^{}\n]*}\\)\\)*")
+	  (looking-at (concat
+			   "\\([a-zA-Z]+\\*?\\)"
+			   "\\(?:<[^<>\n]*>\\)*"
+			   "\\(?:\\[[^][\n]*?\\]\\)*"
+			   "\\(?:<[^<>\n]*>\\)*"
+			   "\\(" (org-create-multibrace-regexp "{" "}" 3) "\\)\\{1,3\\}"))
 	  0))
 	   (value (org-match-string-no-properties substring-match))
 	   (post-blank (progn (goto-char (match-end substring-match))
Index: org-8.2.7b/doc/org.texi
===
--- org-8.2.7b.orig/doc/org.texi
+++ org-8.2.7b/doc/org.texi
@@ -10168,6 +10168,9 @@ any @LaTeX{} environment will be handled
 @code{\begin} and @code{\end} statements appear on a new line, at the
 beginning of the line or after whitespaces only.
 @item
+Commands like \command[...]{...} or \command{...}; the curly brakets could be
+nested up to 3 levels.
+@item
 Text within the usual @LaTeX{} math delimiters.  To avoid conflicts with
 currency specifications, single @samp{$} characters are only recognized as
 math delimiters if the enclosed text contains at most two line breaks, is

Re: [O] org-ref in action

[John Kitchin]

with org-ref

[[cite:tony-2010][page n]]

exports as

\cite[page n]{tony-2010}

and


[[cite:tony-2010][text before link::text after link]]

exports as

\cite[text before link][text after link]{tony-2010}


John

---
John Kitchin
Associate Professor
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
http://kitchingroup.cheme.cmu.edu



On Sun, Jun 29, 2014 at 6:18 AM, Joseph Vidal-Rosset <
joseph.vidal.ros...@gmail.com> wrote:

> Hi John, hello the list,
>
> My question is very simple and it is not unrevelevant vis-à-vis this
> thread, therefore I keep  the same thread.
>
> What  need is to get either  the usual citation format  (often in plain
> style) \cite{one-reference-paper-year} or this one with a mentioned page:
> \cite[page n]{one-reference-paper-year}.
>
> My problem with cite: org-mode format is that I am not able to get the
> second format. Ideally , I want to click on the reference and just to add
> the quoted page.
>
> I do not doubt that this is easy to get in org-mode, but I'm wasting my
> time to find how... if it is possible to get it with org-ref  or via
> another tool, many thanks in advance.
>
> Best regards
>
> Jo.
> ​
>

Re: [O] How to evaluate all source blocks like at export time, anytime?

[Nick Dokos]

Grant Rettke  writes:

> Hi,
>
> In the manual it explains how to disable all source block evaluation
> during export with org-export-babel-evaluate.
>
> I did that, and it is desirable.
>
> However, what is the "right way" to request org to evaluate all of the
> source blocks, in exactly the same manner that would
> have happened during an export with org-export-babel-evaluate non-nil?
>

`org-babel-execute-buffer' I think.

-- 
Nick

[O] Pushing and pulling to google calendar

[Doyley, Marvin M.]

Hi Everybody,

Is there a way to sync org-agenda with google calendar so that I can exploit 
googles calendar reminder.

I wish there was a way to send calendar reminders (pop-up, emails, text message 
)  from org-mode rather than going through google.

Best Wishes,
M


Sent from my iPad

Re: [O] [BUG] Infloop in org-element-inlinetask-parser

[Nicolas Goaziou]

Hello,

Aaron Ecay  writes:

> In the latest checkout of master, I am seeing an infloop in
> org-element-inlinetask-parser.  This originates when that function
> calls back into org-element-at-point to look for a property drawer,
> which moves the point back before the beginning of the inlinetask and
> then attempts to re-enter org-element-inlinetask-parser.

Good catch. This should be fixed. Thank you for the report.


Regards,

-- 
Nicolas Goaziou

Re: [O] [PATCH] curly nested latex fragments

[Nicolas Goaziou]

Hello,

hero...@gentoo.org writes:

> Nesting braces is already implemented in the classic org-latex.el[1],
> and is forward ported into org-element.el.

Thanks for your patch.

I think you are misunderstanding something. I didn't port this
limitation in Org 8. AFAIK it has been there for a long time. See
`org-inside-latex-macro-p' for example.

The main problem with Org < 8 is that every exporter implemented its own
parser for the Org buffer. As you can see, "org-latex.el" was in
contradiction with "org.el".

> Would you like to take a look at the attached patch? Thanks.

I do not mind extending syntax for LaTeX macros a bit if it helps users,
but first, I would like a clear definition of what subset of macros
should be supported in Org.

See, for example,

  http://orgmode.org/worg/dev/org-syntax.html#Entities_and_LaTeX_Fragments

Also, I do not want to add constructs like

  "\\(?:<[^<>\n]*>\\)*"

in this definition, as this isn't supported even in
`TeX-find-macro-end-helper' (from auctex), which I consider as
a reference for macro syntax (i.e. we shouldn't support more than what
is supports).

Eventually, please note that this imply to change not only
"org-element.el", but also "org.el" and possibly other parts where the
limitation is encoded. But first, we need to agree on what exactly
a valid a LaTeX macro is in Org.

> If \ce{^2H} works as above, it is not a problem for me.  Although make
> it configurable is more user-friendly; "^:{}" is already there afterall,
> adding another style feels natural.

It's not about adding another style. "^:{}" allows less (without
changing syntax, because the limitation is done at the export level),
you want to allow more, which implies to change syntax. I don't want the
latter to be configurable.

I explained in this thread why it wasn't possible, for the time being,
to allow a blank character before sub or superscript. This was discussed
on this ML, you may want to search archives.


Regards,

-- 
Nicolas Goaziou

Re: [O] still seeing semi-regular lockups

[Nicolas Goaziou]

Hello,

York Zhao  writes:

> My experience of using `org-mode' (git commit "2824502" and previous versions)
> with Emacs 24.3.91 (git commit "0f0917d") had been a nightmare. I got bitten 
> by
> this bug frequently, I was mad.

I'm sorry about this.

However, just saying that "it had been a nightmare" doesn't help much.
If you can, please try to provide an ECM. I will gladly fix any bug
I can reproduce.

> This was a problem with Emacs 24.3.1 ("3a1ce06") too

Note that this is an entirely different issue, since maint branch
doesn't have a cache. Reporting bugs found there is even more critical
as it is the version that will be shipped with next Emacs release.


Regards,

-- 
Nicolas Goaziou

Re: [O] Pushing and pulling to google calendar

[Jorge A. Alfaro-Murillo]

"Doyley, Marvin M."  writes:

> Hi Everybody,
>
> Is there a way to sync org-agenda with google calendar so that I can
> exploit googles calendar reminder.
>
> I wish there was a way to send calendar reminders (pop-up, emails,
> text message ) from org-mode rather than going through google.

MobileOrg can synchronize to your google calendar, you can then set up
remainders with the calendar app in your phone.

Check (info "(org) MobileOrg")

Best,

Jorge.

[O] org-agenda-files and customize

[David Masterson]

Hmmm.  I just noticed that the following happened:

1. I noticed org-agenda-files was set in the custom-set-variables
section of my .emacs.
2. I removed org-agenda-files from the custom-set-variables section of
my .emacs.
3. I set org-agenda-files in the standard way (C-c [).
4. I notices that org-agenda-files was back in the custom-set-variables
section of my .emacs.

Is that supposed to happen?
-- 
David Masterson
Programmer At Large

Re: [O] org-ref in action

[Eric Schulte]

Joseph Vidal-Rosset  writes:

> Hi John, hello the list,
>
> My question is very simple and it is not unrevelevant vis-à-vis this
> thread, therefore I keep  the same thread.
>
> What  need is to get either  the usual citation format  (often in plain
> style) \cite{one-reference-paper-year} or this one with a mentioned page:
> \cite[page n]{one-reference-paper-year}.
>

With ox-bibtex.el [[cite:(page n)one-reference-paper-year]] will export as

  \cite[page n]{one-reference-paper-year}

>
> My problem with cite: org-mode format is that I am not able to get the
> second format. Ideally , I want to click on the reference and just to add
> the quoted page.
>
> I do not doubt that this is easy to get in org-mode, but I'm wasting my
> time to find how... if it is possible to get it with org-ref  or via
> another tool, many thanks in advance.
>
> Best regards
>
> Jo.
> ​

-- 
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D (see https://u.fsf.org/yw)

Re: [O] org-ref in action

[Joseph Vidal-Rosset]

2014-06-29 20:19 GMT+02:00 Eric Schulte :

> With ox-bibtex.el [[cite:(page n)one-reference-paper-year]] will export as
>
>   \cite[page n]{one-reference-paper-year}
>


Many thanks Eric . It helps a lot !

Best wishes

Jo.

[O] html-encode in mathjax latex fragments

[Eric Schulte]

I noticed equations with "<"'s weren't displaying correctly in HTML
export using mathjax.  The attached patch fixes this by html-encoding
latex fragments for mathjax HTML export.  I imagine this change would be
generally useful and could be applied to master.

Best,
Eric

>From 8c4efca17f2a6fbc836c5a8b6b0f628b6c9fff33 Mon Sep 17 00:00:00 2001
From: Eric Schulte 
Date: Sun, 29 Jun 2014 14:38:03 -0400
Subject: [PATCH] html-encode text in mathjax latex fragments

* lisp/ox-html.el (org-html-format-latex): Html-encode text in mathjax
  latex fragments.
---
 lisp/ox-html.el | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/lisp/ox-html.el b/lisp/ox-html.el
index df392a9..03037f5 100644
--- a/lisp/ox-html.el
+++ b/lisp/ox-html.el
@@ -2610,7 +2610,8 @@ a symbol among `mathjax', `dvipng', `imagemagick', `verbatim' nil
 and t.  See `org-html-with-latex' for more information.  INFO is
 a plist containing export properties."
   (let ((cache-relpath "") (cache-dir ""))
-(unless (eq processing-type 'mathjax)
+(if (eq processing-type 'mathjax)
+	(setq latex-frag (org-html-encode-plain-text latex-frag))
   (let ((bfn (or (buffer-file-name)
 		 (make-temp-name
 		  (expand-file-name "latex" temporary-file-directory
-- 
2.0.0


-- 
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D (see https://u.fsf.org/yw)

[O] Tables of contents for individual sections wanted -- will donate

[D. C. Toedt]

Hi all --

BACKGROUND:  I've been using org-mode to develop the *Common Draft*
annotated collection of business contract clauses, in part for the law
school course in contract drafting that I teach to third-year law students.
 I've been posting the collection as a Creative Commons document at
http://www.CommonDraft.org, and plan to expand and maintain it.

QUESTION:  I'm currently using a single, multi-level table of contents
(TOC) at the beginning of the document.  That ends up being a lot to scroll
through to get to the first chapter.  I'd like instead to have:

   - a one-level "master" TOC at the beginning of the document, listing and
   linking to just the articles (in contracts, "articles" are the same as
   "chapters" in books, that is, the top-level sections); and


   - at the beginning of each article, a TOC listing and linking to the
   subheadings within that article.

EXAMPLE of the desired capability:

[book title:] COMMON DRAFT:  Business Contract Clauses, Annotated and
Explained


SUMMARY OF CONTENTS


1.  Definitions & Usages


2.  Arbitration


3.  Assignment of Agreement


[etc.]


ART. 1.  DEFINITIONS & USAGES


TABLE OF CONTENTS

1.1  Affiliate Status


1.2  Agreement Definition


[etc.]


1.1  Affiliate Status

Two entities are affiliates if one of them controls, is controlled by, or
is under common control of the other, where "control" refers 


1.2  Agreement Definition

The term "this Agreement" refers to this signed document as well as its
exhibits, appendixes, annexes, .


​Suggestions?  ​If it can't currently be done in org-mode but can be
implemented, I'd donate US$100.00 to the org-mode support fund if someone
were to come up with and publish a working solution.  As for doing it
myself in e-lisp, I'm just scratching the surface of e-lisp, so it's not
something I could undertake at this juncture.


Regards,

--D. C.

*D*ell *C*harles "D. C." Toedt III  *(my** last name is pronounced "Tate") *
Attorney and neutral arbitrator -- tech contracts and intellectual property
​Editor, ​​​Common Draft  project:  Model
contract term sheets & clauses, annotated
d...@toedt.com LinkedIn: dctoedt 
Calendar

(redacted)
O: +1 (713) 364-6545C: +1 (713) 516-8968
​​

​
Houston, Texas (Central time zone)

Unless expressly stated otherwise, this message is not intended
to serve as an electronic signature nor as assent to an agreement.

Re: [O] Org Export Latex Hyperref Options Format

[Andrea Rossetti]

Joseph Vidal-Rosset  writes:
> How can I remove this old built-in Org "shadowed"
> by my new Elpa Org ? It seems to me that it should be the best
> solution,

  That time I thought "life is too short to mess with it" :) and simply
ignored that zombie option; it's rare that an option is removed, so
I never faced the same problem again.

  If you still want to try, I guess the built-in Org could be removed
by deleting the elisp code from the directory "/lisp/org".

  Cheers,

Andrea

Re: [O] html-encode in mathjax latex fragments

[Nicolas Goaziou]

Hello,

Eric Schulte  writes:

> I noticed equations with "<"'s weren't displaying correctly in HTML
> export using mathjax.  The attached patch fixes this by html-encoding
> latex fragments for mathjax HTML export.  I imagine this change would be
> generally useful and could be applied to master.

I am a bit puzzled. I just tried exporting the following buffer:

  \(1 < 2\)

and the result looked good. Could you provide an example of a failed
export?


Regards,

-- 
Nicolas Goaziou

Re: [O] Pushing and pulling to google calendar

[Parnell Springmeyer]

MobileOrg is the best solution so far. But there's no bi-directionality,
which is annoying, the sync options in MobileOrg are pretty solid but
getting MobileOrg first setup was enormously confusing for me. I've used
dropbox and btsync to sync and they aren't bad.

I'm working on an actual product for org-mode users to solve the
multi-device synchronization and bi-directional calendar sync problem once
and for all.


On Sun, Jun 29, 2014 at 11:38 AM, Jorge A. Alfaro-Murillo <
jorge.a.alf...@gmail.com> wrote:

> "Doyley, Marvin M."  writes:
>
> > Hi Everybody,
> >
> > Is there a way to sync org-agenda with google calendar so that I can
> > exploit googles calendar reminder.
> >
> > I wish there was a way to send calendar reminders (pop-up, emails,
> > text message ) from org-mode rather than going through google.
>
> MobileOrg can synchronize to your google calendar, you can then set up
> remainders with the calendar app in your phone.
>
> Check (info "(org) MobileOrg")
>
> Best,
>
> Jorge.
>
>
>


-- 
Parnell Springmeyer
Programmer & Entrepreneur
parn...@ixmat.us | http://parnell.io | 0xDCCF89258EAD874A

[O] Always use \hyperref for internal Links in PDF export?

[Bernd Haug]

Hello Orgmoders,

Given a Document:

—
[[Section 1]]

Bla, bla

[[Section 2]]

The blah blah is [[Section1][covered well above]], so let me just say:
[[Section 1]]!
—

I get:

—
…
The blah blah is \hyperref[Section 1]{covered well above}, so let me
just say: \ref{Section 1}
…
—

Is there a any way (without just always writing [[Section 1][Section
1]]) to always get the former behaviour, but just repeating the Title
itself if no explicit link text was provided? That is:

—
…
The blah blah is \hyperref[Section 1]{covered well above}, so let me
just say: \hyperref[Section 1]{Section 1}
…
—

Cheers, Bernd

Re: [O] [PATCH] curly nested latex fragments

[heroxbd]

Hi Nicolas,

Nicolas Goaziou  writes:

> Hello,
>
> hero...@gentoo.org writes:
>
>> Nesting braces is already implemented in the classic org-latex.el[1],
>> and is forward ported into org-element.el.
>
> Thanks for your patch.
>
> I think you are misunderstanding something. I didn't port this
> limitation in Org 8. AFAIK it has been there for a long time. See
> `org-inside-latex-macro-p' for example.

> The main problem with Org < 8 is that every exporter implemented its own
> parser for the Org buffer. As you can see, "org-latex.el" was in
> contradiction with "org.el".

I see, the regex used for latex protection (in org-latex.el) and
footnote guarding (org-footnotes.el org.el) are different.

>> Would you like to take a look at the attached patch? Thanks.
>
> I do not mind extending syntax for LaTeX macros a bit if it helps users,
> but first, I would like a clear definition of what subset of macros
> should be supported in Org.
>
> See, for example,
>
>   http://orgmode.org/worg/dev/org-syntax.html#Entities_and_LaTeX_Fragments

\ce{^{238}U} falls into \NAME POST, doesn't it?

> Also, I do not want to add constructs like
>
>   "\\(?:<[^<>\n]*>\\)*"
>
> in this definition, as this isn't supported even in
> `TeX-find-macro-end-helper' (from auctex), which I consider as
> a reference for macro syntax (i.e. we shouldn't support more than what
> is supports).

Ha, I don't even aware of <...> syntex as a part of the LaTeX macro; I
just copied the regex from org-latex.el.  So let's strip it out, and
advise the users to use explicit LaTeX block for <...> constructs.

+ (looking-at (concat
+  "\\([a-zA-Z]+\\*?\\)"
+  "\\(?:\\[[^][\n]*?\\]\\)*"
+  "\\(" (org-create-multibrace-regexp "{" "}" 3) "\\)\\{1,3\\}"))


> Eventually, please note that this imply to change not only
> "org-element.el", but also "org.el" and possibly other parts where the
> limitation is encoded. But first, we need to agree on what exactly
> a valid a LaTeX macro is in Org.

`org-inside-latex-macro-p' for example? Yeah, definitely.

>> If \ce{^2H} works as above, it is not a problem for me.  Although make
>> it configurable is more user-friendly; "^:{}" is already there afterall,
>> adding another style feels natural.
>
> It's not about adding another style. "^:{}" allows less (without
> changing syntax, because the limitation is done at the export level),
> you want to allow more, which implies to change syntax. I don't want the
> latter to be configurable.
>
> I explained in this thread why it wasn't possible, for the time being,
> to allow a blank character before sub or superscript. This was discussed
> on this ML, you may want to search archives.

Do you mean this[2] and this[3] threads?  I've read them through, and
remotely understood the difficulty coming from the ambiguity of the
syntax.  And as discussed above, the difficulty manifests in the
definition of LaTeX fragments, too.  It is frustrating to deal with
these corner cases, making a well-designed parser framework unnecessary
complex.

At the same time, these syntax sugar is great.  And that's the reason
why we prefer org-mode in composing LaTeX to pristine LaTeX.  There is a
sincere need to compromise the cleanness of the implementation for the
sake of an ambiguous-but-human-intuitive syntax.

To resolve this dilemma, we need a formal (mathematically rigorous) org
syntex specification, like the rules drafted in

  http://orgmode.org/worg/dev/org-syntax.html#Entities_and_LaTeX_Fragments

together with a set of test suites to demonstrate the spec.  There would
be a lot of work, but we could start from embedded LaTeX fragments and
super(sub)scripts/underline.

It might be mentally overwhelming for one single guy to do the spec and
the implementation at the same time, because they require different
mindsets.  The spec is long term and should be stable while the
implementation is always being optimized.  After all, it is considered
good practice to make the two processes independent to each other.

What do you think?

Yours,
Benda

1. 
http://orgmode.org/w/?p=org-mode.git;a=commit;h=88cf58802cc35dee2bc8ff8633b5c842fa7a23b3
2. http://thread.gmane.org/gmane.emacs.orgmode/79735
3. http://thread.gmane.org/gmane.emacs.orgmode/85902

Re: [O] still seeing semi-regular lockups

[York Zhao]

> Yeah, I'm using git emacs, labeled 24.4.50.1

Did you compile Emacs from git? I have never seen the tag 24.4.50.1, are you
sure you didn't have a typo here?

On Sat, Jun 28, 2014 at 10:23 PM, Eric Abrahamsen
 wrote:
> York Zhao  writes:
>
>> My experience of using `org-mode' (git commit "2824502" and previous 
>> versions)
>> with Emacs 24.3.91 (git commit "0f0917d") had been a nightmare. I got bitten 
>> by
>> this bug frequently, I was mad. Some of my `org-drill' entires might have 
>> been
>> damaged to some extent. This was a problem with Emacs 24.3.1 ("3a1ce06") too 
>> but
>> was much better, at least not damaging my `org-drill' flies. I will have to 
>> go
>> back to Emacs 24.3.1. Appears to me that Emacs 24.4 may have some bad issues.
>
> Yeah, I'm using git emacs, labeled 24.4.50.1.
>
>> On Sat, Jun 28, 2014 at 3:27 PM, Eric Abrahamsen
>>  wrote:
>>> Eric Abrahamsen  writes:
>>>
 Nicolas Goaziou  writes:

> Hello,
>
> Eric Abrahamsen  writes:
>
>> None of those three, I'm afraid! It was hanging on a variety of editing
>> operations that, as far as I can tell, had little in common. There's a
>> possibility that they were list-item-related, but really there wasn't
>> much commonality.
>
> FYI, I recently fixed a bug[fn:1] that could introduce uncommon random
> lockups. Hopefully, it may be related to your problem (which is
> different from Daimrod's).

 Thanks for the followup! I was watching Daimrod's thread, and also
 Matt's most recent posting -- that also seemed more relevant to my
 problems, which were almost solely confined to log/state notes. I've
 pulled the fix, and will let you know if I see any more problems.
>>>
>>> After feeling like I was running behind the bus for a few weeks, I may
>>> have finally gotten something useful.
>>>
>>> FWIW I *haven't* seen any log-drawer related lockups for a while now,
>>> not since Nicolas said he fixed some things in that direction. But in
>>> the past couple of days I have had a few flyspell-related lockups, and
>>> finally got an uncompiled backtrace.
>>>
>>> This has happened the same way a few times now. A longish, text-heavy
>>> file, with only three top-level headlines (one of them a footnote
>>> section), and no drawers of any sort anywhere in the document -- very
>>> little Org markup at all, actually. The lockup starts at random, and
>>> SIGUSR2 shows me a very short backtrace related to a flyspell-mode
>>> related advice somewhere (I didn't save this one, it's byte-compiled, if
>>> it's important I'll clean out more compiled files and try to get it
>>> again).
>>>
>>> I recover from that lock, turn off flyspell-mode in my org buffer, and
>>> within three or four commands Org locks up again. This time the
>>> backtrace is related to org cache, here's the one I just got, after
>>> calling org-end-of-line:
>>>
>>> http://pastebin.com/Q0g8DmUa
>>>
>>> Hope that's useful! Let me know if I can provide anything else.
>>>
>>> E
>>>
>>>
>
>

Re: [O] Pushing and pulling to google calendar

[Jorge A. Alfaro-Murillo]

Parnell Springmeyer  writes:

> MobileOrg is the best solution so far. But there's no
> bi-directionality, which is annoying, the sync options in MobileOrg
> are pretty solid but getting MobileOrg first setup was enormously
> confusing for me. I've used dropbox and btsync to sync and they aren't
> bad.

I have been using MobileOrg in multiple computers with Dropbox for quite
a while and I do not have any complaints. I generally try to avoid
Google calendar and use it only for remainders in the Google Now App of
my phone, and to share my calendar with other people. But when I have to
create a new item in the calendar I rather use MobileOrg to create a
capture, and let it handle the synchronization just one way.

Re: [O] org-agenda-files and customize

[Jorge A. Alfaro-Murillo]

David Masterson  writes:

> 2. I removed org-agenda-files from the custom-set-variables section of
> my .emacs.
> 3. I set org-agenda-files in the standard way (C-c [).
> 4. I notices that org-agenda-files was back in the custom-set-variables
> section of my .emacs.
>
> Is that supposed to happen?

Yes. Where do you expect them to be?

If you do not like the custom-set-variables, you have three options (but
you cannot use 'C-c ['):

#+BEGIN_SRC emacs-lisp
  (setq org-agenda-files
(list "file1" "file2" ...))
#+END_SRC

#+BEGIN_SRC emacs-lisp
  (setq org-agenda-files
"path_to_a_directory_that_contains_all_your_files")
#+END_SRC

#+BEGIN_SRC emacs-lisp
  (setq org-agenda-files
"path_to_a_file_with_the_names_and_location_of_all_your_files")
#+END_SRC

Re: [O] still seeing semi-regular lockups

[York Zhao]

I know that doesn't help much except for confirming the problem other people was
suffering. Sorry for the rant. I was too busy and too frustrated.

By the way, what does ECM stands for?

> This is an entirely different issue, since maint branch doesn't have a cache.

I must clarify that what I meant was that I used exactly the same version of
`org-mode', from git repository, with the two Emacs versions. That said, I never
used the `org-mode' version bundled with Emacs. I'm sorry for the confusion.

1. Sometimes when Emacs hangs in `org-mode', "C-g" wouldn't work. Waited
patiently for awhile and "C-g" work again. Pressing "C-g" produced the error
message: "Error in post-command-hook (zfill-post-command-function): (quit)".
Emacs hanged again, waited patiently for awhile until "C-g" worked again and
Emacs revived, but in an unstable state.

2. Other times when Emacs hangs in `org-mode', "C-g" wouldn't work until after
perhaps 20 seconds or so, hitting "C-g" breaks out. Emacs enters a useless
state, nothing works even "C-x C-c" doesn't work, but produces error: "Variable
bind exceeds maximum level" or something.

A few hours ago I switched back to Emacs 24.3.1, problem 1 happened once, but
never had problem 2. And editing in `org-mode' was several times more smooth and
faster. Way better. Again, I want to stress, I was using the same `org-mode'
from git repository (commit "2824502").

Hope this would help a little bit.

On Sun, Jun 29, 2014 at 9:15 PM, York Zhao  wrote:
>> Yeah, I'm using git emacs, labeled 24.4.50.1
>
> Did you compile Emacs from git? I have never seen the tag 24.4.50.1, are you
> sure you didn't have a typo here?
>
> On Sat, Jun 28, 2014 at 10:23 PM, Eric Abrahamsen
>  wrote:
>> York Zhao  writes:
>>
>>> My experience of using `org-mode' (git commit "2824502" and previous 
>>> versions)
>>> with Emacs 24.3.91 (git commit "0f0917d") had been a nightmare. I got 
>>> bitten by
>>> this bug frequently, I was mad. Some of my `org-drill' entires might have 
>>> been
>>> damaged to some extent. This was a problem with Emacs 24.3.1 ("3a1ce06") 
>>> too but
>>> was much better, at least not damaging my `org-drill' flies. I will have to 
>>> go
>>> back to Emacs 24.3.1. Appears to me that Emacs 24.4 may have some bad 
>>> issues.
>>
>> Yeah, I'm using git emacs, labeled 24.4.50.1.
>>
>>> On Sat, Jun 28, 2014 at 3:27 PM, Eric Abrahamsen
>>>  wrote:
 Eric Abrahamsen  writes:

> Nicolas Goaziou  writes:
>
>> Hello,
>>
>> Eric Abrahamsen  writes:
>>
>>> None of those three, I'm afraid! It was hanging on a variety of editing
>>> operations that, as far as I can tell, had little in common. There's a
>>> possibility that they were list-item-related, but really there wasn't
>>> much commonality.
>>
>> FYI, I recently fixed a bug[fn:1] that could introduce uncommon random
>> lockups. Hopefully, it may be related to your problem (which is
>> different from Daimrod's).
>
> Thanks for the followup! I was watching Daimrod's thread, and also
> Matt's most recent posting -- that also seemed more relevant to my
> problems, which were almost solely confined to log/state notes. I've
> pulled the fix, and will let you know if I see any more problems.

 After feeling like I was running behind the bus for a few weeks, I may
 have finally gotten something useful.

 FWIW I *haven't* seen any log-drawer related lockups for a while now,
 not since Nicolas said he fixed some things in that direction. But in
 the past couple of days I have had a few flyspell-related lockups, and
 finally got an uncompiled backtrace.

 This has happened the same way a few times now. A longish, text-heavy
 file, with only three top-level headlines (one of them a footnote
 section), and no drawers of any sort anywhere in the document -- very
 little Org markup at all, actually. The lockup starts at random, and
 SIGUSR2 shows me a very short backtrace related to a flyspell-mode
 related advice somewhere (I didn't save this one, it's byte-compiled, if
 it's important I'll clean out more compiled files and try to get it
 again).

 I recover from that lock, turn off flyspell-mode in my org buffer, and
 within three or four commands Org locks up again. This time the
 backtrace is related to org cache, here's the one I just got, after
 calling org-end-of-line:

 http://pastebin.com/Q0g8DmUa

 Hope that's useful! Let me know if I can provide anything else.

 E


>>
>>

Re: [O] html-encode in mathjax latex fragments

[Nick Dokos]

Nicolas Goaziou  writes:

> Hello,
>
> Eric Schulte  writes:
>
>> I noticed equations with "<"'s weren't displaying correctly in HTML
>> export using mathjax.  The attached patch fixes this by html-encoding
>> latex fragments for mathjax HTML export.  I imagine this change would be
>> generally useful and could be applied to master.
>
> I am a bit puzzled. I just tried exporting the following buffer:
>
>   \(1 < 2\)
>
> and the result looked good. Could you provide an example of a failed
> export?
>
>

See 

   http://docs.mathjax.org/en/latest/tex.html#tex-and-latex-in-html-documents

for some gotchas.

-- 
Nick