Re: [O] [DEV] Bump Emacs requirement to 24.4?

[Suvayu Ali]

Hi Bastien,

On Wed, Aug 19, 2015 at 01:01:29AM +0200, Bastien wrote:
> 
> The maint branch continues to be used to work on minor releases, as it
> has always been used.
> 
> Instead of reverting changes from the master branch (you clearly don't
> want to do that, and I don't either), I suggest we create a new branch
> called "org-8-master" for Org 8.4+, and continue to use master for Org
> 9.x+ (i.e. "major major releases").

I'm slightly confused as-to why this special org-8-master branch is
needed.  As far as I understood from Achim's message (2nd paragraph):

  ,

that so far maint supports Emacs 23.  Although this might have been a
coincidence, without a conscious decision.  It will continue supporting
Emacs 23 until Org 9.  Post Org 9, if required, one can choose to start
a new maint branch called maint23 for continued Emacs 23 support.

Given the above, I do not understand the need for a separate
org-8-master branch.  Is this a gap in communication, or am I missing
something here?

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] [DEV] Bump Emacs requirement to 24.4?

[David Engster]

Bastien writes:
> Emacs 23 and XEmacs support will be officially dropped as of Org 9.0.

Support for XEmacs should be dropped right away; it would just state a
fact, as Org didn't even compile with XEmacs for quite some time now
(and nobody complained).

> I recognize having the manpower to watch after those branches might be
> an issue, but we can overcome it by calling for careful testing before
> major releases.

At least the Buildbot can test the 8.3 branch with older Emacsen. I
already changed that master is only checked with 24.3+.

-David

Re: [O] Add version header to org.el

[Achim Gratz]

Bastien writes:
> So there would be two org.el, one bare, non-generated version, with no
> Version: header, and another one, generated, with all relevant info?

Of course the non-generated version, being in the same directory, would
need to have a different name.  But otherwise, yes.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

[O] Logging the new time on a reschedule.

[Malcolm Purvis]

I would like to log the new time as well as the old when changing the
scheduling or deadline of a task.  I changed the value of
org-log-note-headings to include the new time (%s) in the reschedule
log:

(reschedule .  "Rescheduled from %S to %s on %t")

and set org-log-reschedule to 'time.  However the new time is missing
from the log entry:

- Rescheduled from "[2015-08-21 Fri]" to  on [2015-08-19 Wed 11:03]

I expected this instead:

- Rescheduled from "[2015-08-29 Sat]" to "[2015-09-19 Sat]" on [2015-08-19 
Wed 11:38]

The cause is neither org-schedule nor org-deadline pass the the new time
to org-add-log-setup.  Is there a reason for this?

Malcolm

-- 
   Malcolm Purvis 

Re: [O] [DEV] Bump Emacs requirement to 24.4?

[Bastien]

Hi Nicolas and all,

As Achim said, we may have been miscommunicating, especially on
whether it was about requiring Emacs 23+ or 24.3 vs 24.4.

Here is my decision on this issue:

- the Org 8.x series will be Emacs 23+ compatible.

- the Org 9.x series will be Emacs 24.3+ compatible.

Emacs 23 and XEmacs support will be officially dropped as of Org 9.0.

The maint branch continues to be used to work on minor releases, as it
has always been used.

Instead of reverting changes from the master branch (you clearly don't
want to do that, and I don't either), I suggest we create a new branch
called "org-8-master" for Org 8.4+, and continue to use master for Org
9.x+ (i.e. "major major releases").

This is temporary: once the 9.0 version is released, we can simply use
maint and master as before, and delete org-8-master.

The reason for this is that we need to make room for new features in
the 8.x series, so that these new features will be available to the
Emacs 23 users.

If we drop Emacs 23 support as of Org 8.4, we won't be able to add new
features (e.g. new export backends) for Emacs 23.

I recognize having the manpower to watch after those branches might be
an issue, but we can overcome it by calling for careful testing before
major releases.

Let me know what you think,

-- 
 Bastien

Re: [O] Add version header to org.el

[Bastien]

Hi Achim,

Achim Gratz  writes:

> Since it doesn't appear that there'll be a proper build environment for
> ELPA packages anytime soon, the only way out is to generate org.el.  We
> could do it just for ELPA, although I suggest we go ahead and do it
> across the board.  We can get rid of org-version on the way and put all
> the headers someone wants there as well.  From the new, generated org.el
> we can then require whatever the contents of org.el moves to.

So there would be two org.el, one bare, non-generated version, with no
Version: header, and another one, generated, with all relevant info?

Am I undestanding well?

-- 
 Bastien

Re: [O] outorg issue

[Bastien]

Hi Kaushal,

thanks for sharing your solution.

Kaushal  writes:

> You can fix this issue by manually making changes in your copy of
> outshine as per this PR: https://github.com/tj64/outshine/pull/46/
> files
>
> I use outshine daily and I needed to fix only outshine.el. Probably
> outorg.el needs a similar fix?

Maybe Thorsten would be fine to have you as a maintainer for his
libraries?  Even temporarily?

-- 
 Bastien

Re: [O] Stable releases

[Bastien]

Hi Russell,

Russell Adams  writes:

> Could we reduce the amount of maintenance to the core if we separate
> the rapidly changing plugins to separate projects?

I have a plan to let contrib/* live its own life outside of the core
Org repository.  I hope this will encourage a sense of ownership for
those libraries.

But most bug reports and feature requests are against Org's core,
so I'm not sure a modular approach would really alleviate the task.
Of course, maybe this intuition is wrong, and many bug reports are
against non-core features.

In any case, I think we just need to stick to our "low floor / high
ceiling" approach: be as inclusive and welcome as possible, and give
as much freedom as required to regular contributors.

Finally, if I feel like I need donations to dedicate more time to Org,
I won't hesitate to ask for support.

-- 
 Bastien

Re: [O] beamer_env tag issue with empty headlines

[Prateek Mehta]

On Tue, Aug 18, 2015 at 12:00 PM,  wrote:

>
> Message: 14
> Date: Tue, 18 Aug 2015 14:43:39 +0200
> From: Suvayu Ali 
> To: emacs-orgmode@gnu.org
> Subject: Re: [O] beamer_env tag issue with empty headlines
> Message-ID: <20150818124339.gd18...@chitra.no-ip.org>
> Content-Type: text/plain; charset=us-ascii
>
> On Mon, Aug 17, 2015 at 11:11:59PM -0400, Prateek Mehta wrote:
> >
> > I have a beamer block setup like below, so that it does not have a
> headline.
> >
> >
> > **  :B_block:BMCOL:
> >:PROPERTIES:
> >:BEAMER_col: 0.64
> >:BEAMER_env: block
> >:END:
> >
> > - Some text here
> >
> > When I export it, the beamer environment tags show up in the pdf. This
> was
> > not the case a couple of months ago, when the tags didn't appear in the
> > pdf.
> >
> > If the the headline is not empty, the tags do not show in the pdf and it
> > works as it used to.
>
> I can confirm this behaviour.  I do not know if this is a regression,
> but it is inconsistent for sure.  That said, you can hack around this by
> using \phantom{dummy}.
>
> For now I'm simply getting rid of the tags after specifying the
environments I want to work around the issue. But I do believe that this is
inconsistent behavior.

Prateek



> Hope this helps,
>
> --
> Suvayu
>
> Open source is the future. It sets us free.
>
>

Re: [O] Problem (bug?) evaluating octave code ("function name does not agree with file name)

[Tomas Grigera]

Thanks Eric,

My workaround was to use :session, though not completely satisfactory
(I need to clean up the output).

Your comment made me notice

1. octave reports the problem filename as empty
2. the undefined function call happens at 'line 1', which would not be
the case if the whole code block was copied to a file.

It seems babel is feeding octave the lines one-by-one.  Strange.

Tomas



On Tue, Aug 18, 2015 at 4:38 PM, Eric S Fraga  wrote:
> On Tuesday, 18 Aug 2015 at 10:42, Tomas Grigera wrote:
>> Hello list,
>>
>> I am a very happy user of orgmode and babel.  I recently picked up a
>> document from last year, and found that code blocks that used to
>> evaluate fine now don't.  A code block like this
>
> [...]
>
>> There has been some change, of which I am unaware, in the way babel
>> handles this block that leads to this behaviour.  However, it seems to
>> me that it is a well-formed block and should evaluate fine.  Am I
>> wrong?
>
> Just to confirm that you are not wrong and I ran into this a while ago
> now.  That is, problems with functions defined in the middle of the code
> as opposed to functions in their own .m files.  I didn't have time to
> figure out what was wrong at the time due to deadlines so found other
> ways of doing what I wanted including @(x) function definitions.
>
> The strange thing is that babel seems to not leave any code in the /tmp
> files it creates so I cannot see what code org babel is trying to execute.
>
> --
> : Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.2, Org release_8.3.1-117-gc98729

Re: [O] Emacs batch and bbdb Issue

[Pip Cet]

I've had the same problem, and I found it a little hard to find the
right thing in the source code, so maybe this helps: I think what you
want is "(setq create-lockfiles nil)", which doesn't steal the
lockfile but ignores it; if you need to make sure it's stolen, try
overriding `ask-user-about-lock'. Of course, file locking is there for
a reason, so I strongly suggest making sure your bbdb is being backed
up regularly before trying this.

On 8/18/15, Aric Gregson  wrote:
> Hello,
>
> I have cron set up to send me an email with my org calendar each morning
> as follows:
>
> /usr/local/bin/emacs --batch -l ~/.emacs --eval '(org-batch-agenda "a"
> org-agenda-span (quote day))'
>
> It works fine unless Gnus starts running. When that happens, bbdb is
> taken by Gnus and then the emacs --batch gets stuck because it wants to
> know if emacs should steal the bbdb file.
>
> I use diary in org. I am not sure if there is a way to not use bbdb file
> and still use diary? Is there a way to make stealing the bbdb file the
> default for emacs upon start-up?
>
> Thanks, Aric
>
> --
> ~O
> /\_,
> ###-\  |_
> (*) / (*)
>
>
>

Re: [O] Stable releases

[Russell Adams]

On Tue, Aug 18, 2015 at 07:36:00PM +0200, Bastien wrote:
> Hi Scott,
>
> the main reason why 8.3 was not as "stable" as it should have been is
> that I've been releasing it too quickly, after having been inactive
> way too long.
>
> It's kind of a miracle that Org development could continue without an
> active "official" maintainer for so long, and we owe a lot to Nicolas
> and other contributors for this.

Bastien,

As a Org user since 2006 I've watched and appreciated how much time
and effort yourself and Carsten have put into maintainership. This
significant commitment brings about the following question:

Is Org large enough that it would benefit from being broken into more
pieces?

For instance a stable core that includes only the major mode itself,
which you continue to maintain. This defines the file syntax and
includes core features which require little to no external programs or
libraries.

Then could you break out the exporters, babel, and many of the other
sub-features into "plugins" that could be maintained separately by
others, and they depend back to the core version?

My impression has been that the core Org functionality has been stable
for quite a while, and the org ecosystem grows by leaps and bounds as
new users expand the incredibly flexible syntax to work for their use
case.

Could we reduce the amount of maintenance to the core if we separate
the rapidly changing plugins to separate projects?

Sorry if this has been hashed before, but I felt it appropriate to
ask.

Thanks.

--
Russell Adamsrlad...@adamsinfoserv.com

PGP Key ID: 0x1160DCB3   http://www.adamsinfoserv.com/

Fingerprint:1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3

Re: [O] outorg issue

[Pip Cet]

Hi,
can you confirm the issue only appears when the first line of the
buffer isn't an outline heading? I think it's easy enough to fix then,
and if you like you might want to try the patch I've attached.

It's bugged me for a while that `org-back-to-heading' et al throw
errors when they're used before the first heading, but I haven't
really come up with a better solution.

On 8/18/15, Andreas Leha  wrote:
> Hi Bastien,
>
> Bastien  writes:
>> Hi Andreas,
>>
>> Andreas Leha  writes:
>>
>>> For quite some time now, I have to disable outshine/outorg [1] as it
>>> does give me "Before first heading" (complete backtrace [2]) whenever I
>>> open an org file followed by more issues actually using org mode.
>>
>> Copying Thorsten as the author of outshine.el, hopefully he's be able
>> to dig deeper.
>
> Thanks, but my hopes are low.  Quoting from the top of outshine's github
> readme [1]:
>
> ,
> | events in my life forced me away from Emacs and [...] I won't have the
> | time to fix issues or code new features (though I will apply patches)
> `
>
> Regards,
> Andreas
>
> [1] https://github.com/tj64/outshine
>
>
>
From 753f4e2723c493274d9e55c195296fe5d0b5773e Mon Sep 17 00:00:00 2001
From: Philip 
Date: Tue, 18 Aug 2015 20:24:13 +
Subject: [PATCH] Avoid error when first line of the buffer isn't a heading.

	* outshine.el (outline-hide-sublevels): Avoid error for files that
	don't begin with a heading.
	(outline-cycle): Avoid error for files that don't begin with a
	heading.
---
 outshine.el | 8 +---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/outshine.el b/outshine.el
index 9ccbd1f..aba5271 100644
--- a/outshine.el
+++ b/outshine.el
@@ -1826,8 +1826,9 @@ The old value is stored in
   (setq keep-levels (1- keep-levels))
   (save-excursion
 (goto-char (point-min))
-(hide-subtree)
-(show-children keep-levels)
+(when (outline-on-heading-p)
+  (hide-subtree)
+  (show-children keep-levels))
 (condition-case err
   (while (outline-get-next-sibling)
 (hide-subtree)
@@ -2048,7 +2049,8 @@ may have changed."
 (message "SUBTREE")))
  (t
   ;; Default action: hide the subtree.
-  (hide-subtree)
+  (when (outline-on-heading-p)
+(hide-subtree))
   (unless outshine-cycle-silently
 (message "FOLDED"))
 
-- 
2.5.0

Re: [O] outorg issue

[Kaushal]

I had submitted a pull request to solve this issue on that author's
outshine package page a couple of months back but as Andreas noted, the
author hasn't been able to maintain this stuff due to personal reasons.

You can fix this issue by manually making changes in your copy of outshine
as per this PR: https://github.com/tj64/outshine/pull/46/files

I use outshine daily and I needed to fix only outshine.el. Probably
outorg.el needs a similar fix?

On Tue, Aug 18, 2015 at 3:54 PM Andreas Leha <
andreas.l...@med.uni-goettingen.de> wrote:

> Hi Bastien,
>
> Bastien  writes:
> > Hi Andreas,
> >
> > Andreas Leha  writes:
> >
> >> For quite some time now, I have to disable outshine/outorg [1] as it
> >> does give me "Before first heading" (complete backtrace [2]) whenever I
> >> open an org file followed by more issues actually using org mode.
> >
> > Copying Thorsten as the author of outshine.el, hopefully he's be able
> > to dig deeper.
>
> Thanks, but my hopes are low.  Quoting from the top of outshine's github
> readme [1]:
>
> ,
> | events in my life forced me away from Emacs and [...] I won't have the
> | time to fix issues or code new features (though I will apply patches)
> `
>
> Regards,
> Andreas
>
> [1] https://github.com/tj64/outshine
>
>
>

[O] Emacs batch and bbdb Issue

[Aric Gregson]

Hello,

I have cron set up to send me an email with my org calendar each morning
as follows:

/usr/local/bin/emacs --batch -l ~/.emacs --eval '(org-batch-agenda "a"
org-agenda-span (quote day))'

It works fine unless Gnus starts running. When that happens, bbdb is
taken by Gnus and then the emacs --batch gets stuck because it wants to
know if emacs should steal the bbdb file.

I use diary in org. I am not sure if there is a way to not use bbdb file
and still use diary? Is there a way to make stealing the bbdb file the
default for emacs upon start-up?

Thanks, Aric

-- 
~O
/\_,
###-\  |_
(*) / (*)

Re: [O] outorg issue

[Andreas Leha]

Hi Bastien,

Bastien  writes:
> Hi Andreas,
>
> Andreas Leha  writes:
>
>> For quite some time now, I have to disable outshine/outorg [1] as it
>> does give me "Before first heading" (complete backtrace [2]) whenever I
>> open an org file followed by more issues actually using org mode.
>
> Copying Thorsten as the author of outshine.el, hopefully he's be able
> to dig deeper.

Thanks, but my hopes are low.  Quoting from the top of outshine's github
readme [1]:

,
| events in my life forced me away from Emacs and [...] I won't have the
| time to fix issues or code new features (though I will apply patches)
`

Regards,
Andreas

[1] https://github.com/tj64/outshine

Re: [O] org-mode 3.5.1 emacs 24: invalid-functon 41

[Martin Steffen]

Bastien  gnu.org> writes:

> 
> Hi Martin,
> 
> Martin Steffen  ifi.uio.no> writes:
> 
> > (setq load-path (cons "~/gnu/emacs/24/lisp/org/lisp" load-path))
> > (setq load-path (cons "~/gnu/emacs/24/lisp/org/contrib/lisp" load-path))
> > (add-to-list 'auto-mode-alist '("\\.org\\'" . org-mode))
> 
> After you start Emacs in this minimal mode, can you call
> 
> M-x org-reload RET
> M-x org-version RET
> 
> and report the value?
> 
> Also, grep'ing through your ~/gnu/emacs/ folder to find "41" somewhere
> might help.
> 



thanks for the feedback. What I did in the meantime: I checked out an older
version (I git-checked out a tag  "release_8.3") which made the troubles go
away. 


Now, to re-produce the error: I went back to the last revision which 
showed for me the error and started the minimal emacs (--no-init-file) again.

After starting emacs in the above mentioned  minimal mode (as you proposed),
I called M-x org-reload. That gives the output (1) below.

Org-version gives:


Org-mode version 8.3.1 (release_8.3.1-117-gc98729 @
/ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/)




The grep'ing of the directory does not reveal much. There's some occurences
of "41" in some time stamps or in hex-codes, but not much that seems to
relate to a "function 41". Note also: since I invoke emacs with
"no-init-file" and since my personally extended directories are not entered
to the load-path (apart from the org-subdir), none of the stuff I normally
load from there should play a role in the problem.

In general, I had the impression it's a rather fundamental bug: I disallows
me to type "RETURN" in an org file. More precisely, I cannot type
"RETURN" in "org-mode". If I do, I get the error message

invalid function 41

and the return is not executed (insofar that no new line is added but an
error raised). Due to 
that, org-mode for me in that version is ``broken'' as a cannot enter a new
line at all (except I can "cut-and-paste" a new line  or similar) which is
why I checked-out the previous tag.

.
Martin


-- (1) ---

Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/ob...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/ob-comint...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/ob-core...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/ob-emacs-lisp...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/ob-eval...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/ob-exp...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/ob-keys...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/ob-lob...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/ob-ref...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/ob-table...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/ob-tangle...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/org-compat...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/org-entities...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/org-faces...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/org-footnote...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/org-list...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/org-macro...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/org-macs...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/org-pcomplete...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/org-src...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/org-w3m...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/org-version.el
(source)...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/org.el (source)...
Problems while trying to load feature `org-bbdb'
Problems while trying to load feature `org-bibtex'
Problems while trying to load feature `org-docview'
Problems while trying to load feature `org-gnus'
Problems while trying to load feature `org-info'
Problems while trying to load feature `org-irc'
Problems while trying to load feature `org-mhe'
Problems while trying to load feature `org-rmail'
org-element--set-regexps: Invalid function: 41
Quit
Mark set

Re: [O] Problem (bug?) evaluating octave code ("function name does not agree with file name)

[Eric S Fraga]

On Tuesday, 18 Aug 2015 at 10:42, Tomas Grigera wrote:
> Hello list,
>
> I am a very happy user of orgmode and babel.  I recently picked up a
> document from last year, and found that code blocks that used to
> evaluate fine now don't.  A code block like this

[...]

> There has been some change, of which I am unaware, in the way babel
> handles this block that leads to this behaviour.  However, it seems to
> me that it is a well-formed block and should evaluate fine.  Am I
> wrong?

Just to confirm that you are not wrong and I ran into this a while ago
now.  That is, problems with functions defined in the middle of the code
as opposed to functions in their own .m files.  I didn't have time to
figure out what was wrong at the time due to deadlines so found other
ways of doing what I wanted including @(x) function definitions.

The strange thing is that babel seems to not leave any code in the /tmp
files it creates so I cannot see what code org babel is trying to execute.

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.2, Org release_8.3.1-117-gc98729

Re: [O] re-search-forward hang in org-link-search

[Bastien]

Matthew MacLean  writes:

> No worries. If anything it makes be feel better about my own
> silliness earlier.

Well, I'm good at making people feeling better about their own
silliness, so you're most welcome.

-- 
 Bastien

Re: [O] Stable releases

[Scott Randby]

On 08/18/2015 01:36 PM, Bastien wrote:

Hi Scott,

the main reason why 8.3 was not as "stable" as it should have been is
that I've been releasing it too quickly, after having been inactive
way too long.

It's kind of a miracle that Org development could continue without an
active "official" maintainer for so long, and we owe a lot to Nicolas
and other contributors for this.

So all the advice you got is good, but think of 8.3 as a "come back"
release, with problems that are largely due to me not paying attention
enough to all those small details that make a good release.

The cure is to deliver major releases at a steady pace, and I'm sure
having a "release team" will help a lot.


I've learned a lot from the advice I've been given, and I'm now better 
equipped to handle updates.




In the meantime, `org-latex-with-hyperref' will be back in 8.3.2 as
I don't see why we needed to remove this option too.


I appreciate this a great deal. It will make my life easier to have this 
variable back in Org.


Scott Randby



Thanks,

Re: [O] re-search-forward hang in org-link-search

[Matthew MacLean]

No worries. If anything it makes be feel better about my own silliness
earlier.

On Tue, Aug 18, 2015 at 11:54 AM, Bastien  wrote:

> Matthew MacLean  writes:
>
> > Maybe the recursive-whitespace Regular Expressions that Pip Cet
> > mentioned are not Emacs freezers in Emacs 25?
>
> No... this is just me using the patched version, sorry for the noise.
>
> --
>  Bastien
>

Re: [O] re-search-forward hang in org-link-search

[Pip Cet]

I'm using Emacs 25.0.50.26, for what it's worth, and they still freeze
Emacs here. I don't recall precisely when the problematic regular
expressions were introduced, though, that might have been after 8.3.1?

On 8/18/15, Matthew MacLean  wrote:
> Fascinating.
>
> Maybe the recursive-whitespace Regular Expressions that Pip Cet mentioned
> are not Emacs freezers in Emacs 25?
>
> On Tue, Aug 18, 2015 at 11:30 AM, Bastien  wrote:
>
>> Hi Matthew,
>>
>> I've no problem with the link in hang.org.
>>
>> This is with Org 8.3.1 and Emacs 25.0.50.18.
>>
>> --
>>  Bastien
>>
>

Re: [O] re-search-forward hang in org-link-search

[Bastien]

Matthew MacLean  writes:

> Maybe the recursive-whitespace Regular Expressions that Pip Cet
> mentioned are not Emacs freezers in Emacs 25?

No... this is just me using the patched version, sorry for the noise.

-- 
 Bastien

Re: [O] Stable releases

[Bastien]

Bastien  writes:

> This is not too late -- can you add a note in etc/ORG-NEWS in maint
> about this change?

Forget about this, I've reintroduced org-latex-with-hyperref.

-- 
 Bastien

Re: [O] Stable releases

[Bastien]

Hi Scott,

the main reason why 8.3 was not as "stable" as it should have been is
that I've been releasing it too quickly, after having been inactive
way too long.

It's kind of a miracle that Org development could continue without an
active "official" maintainer for so long, and we owe a lot to Nicolas
and other contributors for this.

So all the advice you got is good, but think of 8.3 as a "come back"
release, with problems that are largely due to me not paying attention
enough to all those small details that make a good release.

The cure is to deliver major releases at a steady pace, and I'm sure
having a "release team" will help a lot.

In the meantime, `org-latex-with-hyperref' will be back in 8.3.2 as
I don't see why we needed to remove this option too.

Thanks,

-- 
 Bastien

Re: [O] Add version header to org.el

[Achim Gratz]

Rasmus writes:
>>> Is there any issues with adding a version header to org.el in maint and
>>> master?
>>
>> I don't think so. It may require to update README_maintainer
>> accordingly.
>
> Done.

Please revert that change.  It's messing with the version numbers on
ELPA since (as I suspected) the idea of using the version from the
header comments in the (main) package file is half-baked.

Since it doesn't appear that there'll be a proper build environment for
ELPA packages anytime soon, the only way out is to generate org.el.  We
could do it just for ELPA, although I suggest we go ahead and do it
across the board.  We can get rid of org-version on the way and put all
the headers someone wants there as well.  From the new, generated org.el
we can then require whatever the contents of org.el moves to.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs

Re: [O] re-search-forward hang in org-link-search

[Matthew MacLean]

Fascinating.

Maybe the recursive-whitespace Regular Expressions that Pip Cet mentioned
are not Emacs freezers in Emacs 25?

On Tue, Aug 18, 2015 at 11:30 AM, Bastien  wrote:

> Hi Matthew,
>
> I've no problem with the link in hang.org.
>
> This is with Org 8.3.1 and Emacs 25.0.50.18.
>
> --
>  Bastien
>

Re: [O] re-search-forward hang in org-link-search

[Bastien]

Hi Matthew,

I've no problem with the link in hang.org.

This is with Org 8.3.1 and Emacs 25.0.50.18.

-- 
 Bastien

Re: [O] org-block-background in 8.3.1?

[Bastien]

Hi Sébastien,

Sebastien Vauban 
writes:

> Really, it has been removed because of a problem when ps-print'ing an
> Org buffer -- though the bug was to find in `ps-def.el' and not in Org,
> as reported by Stefan Monnier [1].  It should have been fixed there
> instead.

Yes, indeed.

>> I'm not aware of anything that has been introduced in its place.
>
> I'm planning to reintroduce it as an optional feature.  At least in my
> personal Git repository, if that's not accepted in Org core.

If you can find an implementation that does not rely on overlays,
I'm fine with it - overlays have inherent scalability issues, and
I'm reluctant using them for something as pervasive as code blocks
background.

Thanks,

-- 
 Bastien

Re: [O] Stable releases

[Bastien]

Hi Nicolas,

Nicolas Goaziou  writes:

> I'm not sure to understand. What is wrong with setting
> `org-latex-hyperref-template' to the empty string?
>
> This change was introduced in Feb 2014. It is a step forward since we
> move from an opt-in/opt-out to a full customizable template.
>
> I overlooked the fact that this replacement wasn't signaled in ORG-NEWS,
> tho.

This is not too late -- can you add a note in etc/ORG-NEWS in maint
about this change?

Thanks,

-- 
 Bastien

Re: [O] [OFF TOPIC] almost giving up on emacs email..looking for advice?

[Bastien]

Hi Matt,

Matt Lundin  writes:

> Certainly! These are the settings I have:

I'm using this now and it works well, thanks a lot!

-- 
 Bastien

Re: [O] M-x org-publish in 8.3.1 results in error "org-check-agenda-file: Wrong type argument: stringp, nil"

[Bastien]

Omid  writes:

> user-error: No language for src block: (unnamed)

This suggests to look for a #+begin_src block with no language name.

-- 
 Bastien

Re: [O] outorg issue

[Bastien]

Hi Andreas,

Andreas Leha  writes:

> For quite some time now, I have to disable outshine/outorg [1] as it
> does give me "Before first heading" (complete backtrace [2]) whenever I
> open an org file followed by more issues actually using org mode.

Copying Thorsten as the author of outshine.el, hopefully he's be able
to dig deeper.

Thanks,

-- 
 Bastien

Re: [O] Emacspeak and org mode (fwd)

[Bastien]

Hi Tim,

Jude DaShiell forwarded your message about Org+Emacsspeak problems.

Some of the problem may be the result of a wrong installation of Org.
Some other may be due to Emacsspeak, which I don't use.

Please read http://orgmode.org/manual/Installation.html again to make
sure you install Org correctly.

If you still encounter problems, please report them on this mailing
list, providing a minimal configuration and example, so that we can
more easily debug it, we will try to fix those that are directly
related to Org.

Thanks,

-- 
 Bastien

Re: [O] helm-mode-org-set-tags adding additional tags

[Bastien]

PS: also, if an external package is used, please explain how to
install and use it for the debugging purpose.

-- 
 Bastien

Re: [O] helm-mode-org-set-tags adding additional tags

[Bastien]

Hi Stephen,

"Stephen J. Barr"  writes:

> I am using org-mode 8.2.10 with helm. When I am adding tags to a
> headline, the first tag offers me completions of all possible tags in
> the file. However, if I go back later and add additional tags, I am
> not offered completion. How can I fix this?

I'm not clear on how to reproduce this problem.

Can you go through the details step by step?

Thanks,

-- 
 Bastien

[O] Org Babel blocks exports dollar signs to LaTeX verbatim

[Matthew MacLean]

When working with Org Babel source code blocks, if I have a dollar sign in
my code and export it to PDF using LaTeX, it appears to parse as an
internal link. (Maybe?)

This is what it looks like:
[image: Inline image 1]
That comes from the following source code block:

#+BEGIN_SRC sql :eval no :var id=1
  SELECT * FROM blah
WHERE id=$id
#+END_SRC

The resulting LaTeX from the source code block is:

\begin{minted}[]{sql}
SELECT * FROM blah
  WHERE id=$id
\end{minted}

I have verified that SQL is not the only block type to do this by having a
Ruby block with nothing except a "$" in it, and got the same result.

This happens as late as commit 682bb962f3934cd50d28a9b2d0b0e0fb85746a03
with Pygments 1.6+dfsg-1ubuntu1 and the Minted included with
texlive-latex-extra 2013.20140215-2 on Linux Mint 17.2 and Emacs 24.5.1
(x86_64).

I have attached my Org Mode config (Not the actual config, but a few setqs
and a list of things that customize spits out), the test Org file, its
output, as well as the PDF generated from that.

Is this a bug? Or is there something wrong with my configuration?

Thanks.
;; From my dotemacs
(setq-default indent-tabs-mode nil)
(setq org-src-fontify-natively t)
(setq org-export-latex-listings 'minted)

;; From customize
(list
 '(org-agenda-window-setup (quote current-window))
 '(org-babel-load-languages
   (quote
((emacs-lisp . t)
 (lisp . t)
 (dot . t)
 (java . t)
 (js . t)
 (http . t)
 (ruby . t)
 (sh . t)
 (C . t)
 (sql . t
 '(org-confirm-babel-evaluate nil)
 '(org-drill-optimal-factor-matrix
   (quote
((2
  (2.6 . 2.588))
 (1
  (2.36 . 3.86)
  (1.96 . 3.58)
  (2.5 . 4.0)
 '(org-export-backends (quote (ascii html icalendar latex man md odt)))
 '(org-export-latex-listings (quote minted) t)
 '(org-indirect-buffer-display (quote current-window))
 '(org-latex-listings (quote minted))
 '(org-latex-minted-langs
   (quote
((emacs-lisp "common-lisp")
 (sql "sql")
 (cc "c++")
 (cperl "perl")
 (shell-script "bash")
 (caml "ocaml")
 (lisp "common-lisp"
 '(org-latex-packages-alist (quote (("" "minted" t
 '(org-latex-pdf-process
   (quote
("pdflatex -shell-escape -interaction nonstopmode -output-directory %o %f" "pdflatex -shell-escape -interaction nonstopmode -output-directory %o %f" "pdflatex -shell-escape -interaction nonstopmode -output-directory %o %f")))
 '(org-link-frame-setup
   (quote
((vm . vm-visit-folder-other-frame)
 (vm-imap . vm-visit-imap-folder-other-frame)
 (gnus . org-gnus-no-new-news)
 (file . find-file)
 (wl . wl-other-frame
 '(org-modules
   (quote
(org-bbdb org-bibtex org-docview org-gnus org-info org-irc org-mhe org-rmail org-w3m org-drill)))
 '(org-src-fontify-natively t)
 '(org-src-lang-modes
   (quote
(("ocaml" . tuareg)
 ("elisp" . emacs-lisp)
 ("ditaa" . artist)
 ("asymptote" . asy)
 ("dot" . fundamental)
 ("sqlite" . sql)
 ("calc" . fundamental)
 ("C" . c)
 ("cpp" . c++)
 ("screen" . shell-script)
 ("java" . java)
 ("http" . ob-http)
 ("C++" . c++
 '(org-src-window-setup (quote current-window))
 '(org-todo-keywords
   (quote
((sequence "TODO(t)" "|" "DONE(d)")
 (sequence "REPORT(r)" "BUG(b)" "KNOWNCAUSE(k)" "|" "FIXED(f)")
 (sequence "|" "CANCELLED(c)")


dollar.org
Description: Binary data


dollar.tex
Description: TeX document


dollar.pdf
Description: Adobe PDF document

Re: [O] [PATCH] org.texi: Fix case of `results' header-arg node.

[Bastien]

Hi Grant,

Grant Rettke  writes:

> Lower-case the results header arg node in /doc/org.texi. Right now it
> is upper-cased.

Applied, thanks.

-- 
 Bastien

Re: [O] org-mode 3.5.1 @ emacs 24: invalid-functon 41

[Bastien]

Hi Martin,

Martin Steffen  writes:

> (setq load-path (cons "~/gnu/emacs/24/lisp/org/lisp" load-path))
> (setq load-path (cons "~/gnu/emacs/24/lisp/org/contrib/lisp" load-path))
> (add-to-list 'auto-mode-alist '("\\.org\\'" . org-mode))

After you start Emacs in this minimal mode, can you call

M-x org-reload RET
M-x org-version RET

and report the value?

Also, grep'ing through your ~/gnu/emacs/ folder to find "41" somewhere
might help.

-- 
 Bastien

Re: [O] [PATCH] Only use HTML5 fancy elements in HTML5

[Bastien]

Hi Eric,

Eric Abrahamsen  writes:

> Here's another patch with a new function.

Applied, thanks.

-- 
 Bastien

Re: [O] [ANN] Syntax checker now in master

[Bastien]

Hi Nicolas,

Nicolas Goaziou  writes:

> False positives are acceptable when "Trust" level is low. Of course, it
> could be a bug in the checker, too.

"Incorrect location for PROPERTIES drawer" warnings are always
reported as "high" trust so far.

> In any case, you asked to remove the library from master (it requires
> Emacs 24.3). I think bug reports can wait.

Of course, fixing those problems can wait.  No hurry.  I will report
them when I have time for this.

Thanks,

-- 
 Bastien

Re: [O] [PATCH] Fix property name completion

[Bastien]

Hi Alexey,

thanks for the patch.  However, this is not a tiny change, as the
cumulated changes are larger than 15 lines¹.

If you want to sign the FSF copyright assignment, please see:

http://orgmode.org/cgit.cgi/org-mode.git/plain/request-assign-future.txt

Thanks!

¹ http://bzr.savannah.gnu.org/lh/emacs/trunk/annotate/head:/etc/CONTRIBUTE

-- 
 Bastien

Re: [O] element-debug-mode breaks capture

[Bastien]

Samuel Wales  writes:

> in maint when i capture, i often get this:
>
>   Error running timer `org-element--cache-sync': (wrong-type-argument
> integer-or-marker-p nil)

I also had a lot of these recently.

I'm now turning org-element-use-cache off and I don't see real issue
when not using it.

Nicolas, what's the real benefit of using the cache?  Is it with
large files?  With frequent updates of the structure?  What actions
are the most impacted by not using the cache?

Thanks,

-- 
 Bastien

Re: [O] A bug with expanding headlines of the sparse tree?

[Bastien]

Hi Meir,

Meir Goldenberg  writes:

> Now, if we do C-/ T and give TODO for the keyword, then we correctly
> get:
>
> * TODO Task1 [0/1]...
>
> However, if we press Tab on this line, then the whole content,
> including next headline (the one marked FUTURE) shows up, which seems
> to be wrong.

I cannot reproduce this problem here with Org 8.3.1.

Can you upgrade and try again?

Please be aware of this changelog when upgrading:

  *** New variable to control visibility when revealing a location

  org-show-following-heading, org-show-siblings, org-show-entry-below
  and org-show-hierarchy-above no longer exist.  Instead, visibility is
  controlled through a single variable: org-show-context-detail, which
  see.

Thanks,

-- 
 Bastien

Re: [O] Emacs-Orgmode Archive search fails

[Bastien]

Hi Charles,

Charles Millar  writes:

> I just tried the mail list archive search again with simply "latex"
> and "LaTeX" and still the one and only result is to a February 2015
> message. Other similar simple searches yield nothing.

OK.  I wrote to webmast...@gnu.org again about this problem.

-- 
 Bastien

Re: [O] Bug: src block face [8.3.1 (8.3.1-56-g17a225-elpaplus @ /Users/ctanis/.emacs.d/elpa/org-plus-contrib-20150817/)]

[Kyle Meyer]

"Tanis, Craig"  writes:

> I don't suppose there's some way to get the best of both worlds:
> visibly distinct org-blocks with mode-specific keyword fontification?

Not that I'm aware of (but see the recent thread on the removed
org-block-background face [1]).  You could change the
org-block-begin-line and org-block-end-line faces to be very distinct,
but that isn't the actual source block.

[1] http://thread.gmane.org/gmane.emacs.orgmode/99902.

--
Kyle

Re: [O] [ANN] orgtbl-join

[Bastien]

Hi Thierry,

Thierry Banel  writes:

> As 8.3 is already out, it should be added to an upcoming release.
> (Sorry Bastien, I missed your message, I was off-line for a few
> days).
>
> I will submit a patch to the mailing-list, including a translation of
> the documentation (https://github.com/tbanel/orgtbljoin) to the texi
> format.

Great, thanks in advance!

-- 
 Bastien

Re: [O] Bug: src block face [8.3.1 (8.3.1-56-g17a225-elpaplus @ /Users/ctanis/.emacs.d/elpa/org-plus-contrib-20150817/)]

[Tanis, Craig]

Aha!  In my configuration, I was fontifying org-block to use a different 
background color and font family.  I don't suppose there's some way to get the 
best of both worlds: visibly distinct org-blocks with mode-specific keyword 
fontification?

Thanks,
Craig

> On Aug 18, 2015, at 10:36 AM, Kyle Meyer  wrote:
> 
> "Tanis, Craig"  writes:
> 
>> SRC blocks don't show correct face when a language is specified.
>> 
>> #+begin_src
>>  correctly shows in 'org-block face
>> #+end_src
>> 
>> #+begin_src language
>> incorrectly shows in 'default face
>> #+end_src
> 
> I suspect that in your second block you're using text the would have the
> default face in a buffer for that language.
> 
> Depending on the value of org-src-fontify-natively, Org will try to
> highlight the block according to the language.
> 
> So
> 
> #+begin_src
>  (message "yes")
> #+end_src
> 
> will use the org-block face, but
> 
> #+begin_src elisp
>  (message "yes")
> #+end_src
> 
> will highlight according to emacs-lisp-mode.
> 
> If org-src-fontify-natively is nil, the org-block face will be used for
> the second block as well.
> 
> --
> Kyle


Craig Tanis, Ph.D.
UTC Computer Science
craig-ta...@utc.edu

Re: [O] current status of citation syntax discussion

[Joseph Vidal-Rosset]

2015-08-18 9:53 GMT+02:00 Joseph Vidal-Rosset :

> Thanks to Eric's example (here :
> https://lists.gnu.org/archive/html/emacs-orgmode/2014-01/msg01262.html )
> I have succeeded to use ox-bibtex.el. \cite{} in the org file works both
> for html and latex.
>
> Nevertheless, I wonder how to get for org-file the org citation syntax
> [[cite: ]] instead of \cite{} when I choose a reference from my
> references.bib file . Is it possible to change this point in order to get
> the same org file than in Eric's example ?


I just finded a solution here :
https://tincman.wordpress.com/2011/01/04/research-paper-management-with-emacs-org-mode-and-reftex/

and here is the adaptation of the code in my init.el :

(defun org-mode-reftex-setup ()
  (load-library "reftex")
  (and (buffer-file-name) (file-exists-p (buffer-file-name))
   (progn
 ;enable auto-revert-mode to update reftex when bibtex file changes on
disk
 (global-auto-revert-mode t)
 (reftex-parse-all)
 ;add a custom reftex cite format to insert links
 (reftex-set-cite-format
  '((?c . "[[cite:%l]]")
  (define-key org-mode-map (kbd "C-c ]") 'reftex-citation))

(add-hook 'org-mode-hook 'org-mode-reftex-setup)

with # \bibliography{reforg} at the beginning of my .org file, referring to
my .bib file, it works.

Best wishes,

Jo.

Re: [O] Bug: src block face [8.3.1 (8.3.1-56-g17a225-elpaplus @ /Users/ctanis/.emacs.d/elpa/org-plus-contrib-20150817/)]

[Kyle Meyer]

"Tanis, Craig"  writes:

> SRC blocks don't show correct face when a language is specified.
>
> #+begin_src
>   correctly shows in 'org-block face
> #+end_src
>
> #+begin_src language
> incorrectly shows in 'default face
> #+end_src

I suspect that in your second block you're using text the would have the
default face in a buffer for that language.

Depending on the value of org-src-fontify-natively, Org will try to
highlight the block according to the language.

So

#+begin_src
  (message "yes")
#+end_src

will use the org-block face, but

#+begin_src elisp
  (message "yes")
#+end_src

will highlight according to emacs-lisp-mode.

If org-src-fontify-natively is nil, the org-block face will be used for
the second block as well.

--
Kyle

[O] Bug: Priorities not inheriting [8.3.1 (8.3.1-56-g17a225-elpa @ /Users/luke/.emacs.d/elpa/org-20150817/)]

[Luke Amdor]

Given a test.org with:

* [#B] Test
** TODO one


When I do the agenda to find TODO headlines with priority B I would expect
it to find the "TODO one", however it doesn't. I'm very sure this regressed
when upgrading to 8.3.1, as it worked fine in 8.3.0. Thanks!


Emacs  : GNU Emacs 24.5.1 (x86_64-apple-darwin14.1.0, NS
apple-appkit-1344.72)
 of 2015-04-17 on MacBook-Pro.local
Package: Org-mode version 8.3.1 (8.3.1-56-g17a225-elpa @
/Users/luke/.emacs.d/elpa/org-20150817/)

(add-to-list 'load-path (expand-file-name "./org-mode/lisp"))
(add-to-list 'load-path (expand-file-name "./org-mode/contrib/lisp" t))

(setq inhibit-startup-message t)

(setq org-use-property-inheritance t)

(setq org-agenda-files (list "test.org"))

(setq org-agenda-custom-commands
  '(("t" "Test" ((tags-todo "+PRIORITY=\"B\"")


Luke

[O] Problem (bug?) evaluating octave code ("function name does not agree with file name)

[Tomas Grigera]

Hello list,

I am a very happy user of orgmode and babel.  I recently picked up a
document from last year, and found that code blocks that used to
evaluate fine now don't.  A code block like this

#+BEGIN_SRC octave
1;
function y=dup(x)
  y=2*x;
end

dup(2)
#+END_SRC

fails with

: warning: function name 'dup' does not agree with function file name ''
: error: 'dup' undefined near line 1 column 1

on evaluating, despite the "1;" trick at the beginning.  Saving to
foo.m and running from octave works fine.

I'm using

Emacs 24.4.1
Org-mode version 8.3.1 (8.3.1-56-g17a225-elpa)
GNU Octave, version 3.8.2


There has been some change, of which I am unaware, in the way babel
handles this block that leads to this behaviour.  However, it seems to
me that it is a well-formed block and should evaluate fine.  Am I
wrong?

Thanks in advance

Tomas

[O] Bug: src block face [8.3.1 (8.3.1-56-g17a225-elpaplus @ /Users/ctanis/.emacs.d/elpa/org-plus-contrib-20150817/)]

[Tanis, Craig]

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.


SRC blocks don't show correct face when a language is specified.

#+begin_src 
  correctly shows in 'org-block face
#+end_src

#+begin_src language
incorrectly shows in 'default face
#+end_src





Emacs  : GNU Emacs 24.5.1 (x86_64-apple-darwin14.3.0, NS apple-appkit-1347.57)
of 2015-04-15 on zartan
Package: Org-mode version 8.3.1 (8.3.1-56-g17a225-elpaplus @ 
/Users/ctanis/.emacs.d/elpa/org-plus-contrib-20150817/)

current state:
==
(setq
org-tab-first-hook '(yas/org-very-safe-expand org-hide-block-toggle-maybe
  org-babel-hide-result-toggle-maybe 
org-babel-header-arg-expand)
org-goto-interface 'outline-path-completion
org-speed-command-hook '(org-speed-command-default-hook 
org-babel-speed-command-hook)
org-agenda-diary-file "~/Dropbox/org/diary.org"
org-mac-grab-Chrome-app-p nil
org-occur-hook '(org-first-headline-recenter)
org-metaup-hook '(org-babel-load-in-session-maybe)
org-log-done 'time
org-confirm-shell-link-function 'yes-or-no-p
org-image-actual-width nil
org-mac-grab-Firefox-app-p nil
org-startup-folded nil
org-yank-folded-subtrees nil
org-list-allow-alphabetical t
org-special-ctrl-a/e 'reversed
org-after-todo-state-change-hook '(org-clock-out-if-current)
org-src-mode-hook '(org-src-babel-configure-edit-buffer
 org-src-mode-configure-edit-buffer)
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-babel-pre-tangle-hook '(save-buffer)
org-mode-hook '(#[nil "\301\302\303#\207"
   [org-mode-map define-key "g" org-mac-grab-link] 4]
 #[nil "\300\301\302\303\304$\207"
   [org-add-hook change-major-mode-hook org-show-block-all 
append
local]
   5]
 #[nil "\300\301\302\303\304$\207"
   [org-add-hook change-major-mode-hook 
org-babel-show-result-all
append local]
   5]
 org-babel-result-hide-spec org-babel-hide-all-hashes 
org-eldoc-load
 (lambda nil (make-variable-buffer-local (quote 
yas/trigger-key))
  (setq yas/trigger-key [tab])
  (if (member (quote yas/org-very-safe-expand) 
org-tab-first-hook)
   org-tab-first-hook
   (setq org-tab-first-hook
(cons (quote yas/org-very-safe-expand) org-tab-first-hook))
   )
  (define-key yas/keymap [tab] (quote yas-next-field)))
 (lambda nil (local-set-key "\220" (quote org-backward-element))
  (local-set-key "\216" (quote org-forward-element))
  (local-set-key "\373" (quote backward-paragraph))
  (local-set-key "\375" (quote forward-paragraph))
  (local-set-key "\225" (quote org-up-list-or-element))
  (local-set-key "\204" (quote org-down-element))
  (local-set-key "\367" (quote org-refile-fullpath))
  (local-set-key "\342" (quote org-mark-ring-goto))
  (local-set-key "\356" (quote org-next-block))
  (local-set-key "\360" (quote org-previous-block))
  (auto-fill-mode 1) (toggle-truncate-lines -1)
  (local-set-key (kbd "C-c SPC") (quote ace-jump-mode)))
 )
org-refile-targets '((nil :maxlevel . 9))
org-outline-path-complete-in-steps nil
org-archive-hook '(org-attach-archive-delete-maybe)
org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point org-babel-execute-safely-maybe)
org-refile-use-outline-path t
org-directory "~/Dropbox/org"
org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
  org-cycle-show-empty-lines
  org-optimize-window-after-visibility-change)
org-archive-default-command 'org-toggle-archive-tag
org-hide-emphasis-markers t
org-catch-invisible-edits 'smart
org-babel-tangle-lang-exts '(("python" . "py") ("java" . "java") ("D" . "d")
  ("C++" . "cpp") ("perl" . "pl") ("emacs-lisp" . 
"el")
  ("elisp" . "el"))
org-confirm-elisp-link-function 'yes-or-no-p
org-metadown-hook '(org-babel-pop-to-session-maybe)
org-log-into-drawer t
org-ditaa-jar-path "/usr/local/Cellar/ditaa/0.9/libexec/ditaa0_9.jar"
org-completion-use-ido t
org-babel-load-languages '((emacs-lisp . t) (perl . t) (C . t) (java . t)
(python . t) (ditaa . t) (dot . t) (gnuplot . t)
(octave . t) (calc . t) (sh . t))
org-cycle-global-at-bob t

org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
)



Craig Tanis, Ph.D.
UTC Computer Science
crai

[O] org-mode 3.5.1 @ emacs 24: invalid-functon 41

[Martin Steffen]

Hi,

I have recently git-pulled the latest org-mode (and make-compiled it).
Since the upgrade, org is basically broken. If I visit a file, emacs answers
with invalid-function 41 (I have debug-on-error to "t", but it does not give
much info where it chokes).

I have now org-version 3.5.1. Before the upgrade, it was, I assume some
3.5.0 (maybe 3.5.0h, and that worked). 

emacs-version: 24.5.2


If I use emacs 23.1, the problem goes away.

To avoid interference with too many loaded packages (including org-features).
I started emacs with

   emacs --no-init-file

and eval'ed just the following 3 lines


(setq load-path (cons "~/gnu/emacs/24/lisp/org/lisp" load-path))
(setq load-path (cons "~/gnu/emacs/24/lisp/org/contrib/lisp" load-path))
(add-to-list 'auto-mode-alist '("\\.org\\'" . org-mode))


Here's some other errors in the *Messages* buffer:




Problems while trying to load feature `org-bbdb'
Problems while trying to load feature `org-bibtex'
Problems while trying to load feature `org-docview'
Problems while trying to load feature `org-gnus'
Problems while trying to load feature `org-info'
Problems while trying to load feature `org-irc'
Problems while trying to load feature `org-mhe'
Problems while trying to load feature `org-rmail'
File mode specification error: (invalid-function 41)

[O] beamer_env tag issue with empty headlines

[Prateek Mehta]

Hi,

I have a beamer block setup like below, so that it does not have a headline.


**  :B_block:BMCOL:
   :PROPERTIES:
   :BEAMER_col: 0.64
   :BEAMER_env: block
   :END:

- Some text here

When I export it, the beamer environment tags show up in the pdf. This was
not the case a couple of months ago, when the tags didn't appear in the
pdf.

If the the headline is not empty, the tags do not show in the pdf and it
works as it used to.

Has there been a recent change that introduced this?

I am using emacs 24.5.1 and org 8.3.1.

Thanks,

Prateek

Re: [O] beamer_env tag issue with empty headlines

[Suvayu Ali]

On Mon, Aug 17, 2015 at 11:11:59PM -0400, Prateek Mehta wrote:
> 
> I have a beamer block setup like below, so that it does not have a headline.
> 
> 
> **  :B_block:BMCOL:
>:PROPERTIES:
>:BEAMER_col: 0.64
>:BEAMER_env: block
>:END:
> 
> - Some text here
> 
> When I export it, the beamer environment tags show up in the pdf. This was
> not the case a couple of months ago, when the tags didn't appear in the
> pdf.
> 
> If the the headline is not empty, the tags do not show in the pdf and it
> works as it used to.

I can confirm this behaviour.  I do not know if this is a regression,
but it is inconsistent for sure.  That said, you can hack around this by
using \phantom{dummy}.

Hope this helps,

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] Bug: babel load error [8.3.1 (8.3.1-16-gf6aa53-elpaplus @ /Users/chromiak/.emacs.d/elpa/org-plus-contrib-20150810/)]

[Kyle Meyer]

"Chromiak, Walter"  writes:

>> Uninstall Org from the package-list-packages menu, restart Emacs making
>> sure that Org has not been loaded, and then install Org again from the
>> package-list-packages menu.

> Thank you. I did exactly that, twice, once with the gnu package-list
> version and once with the org package-list version. Neither made a
> difference in the babel error problem.

Are you sure the builtin version of Org is not being loaded (perhaps in
your config) before you're installing?  Have you tried with 'emacs -Q'
and evaluating only package-related setup?

--
Kyle

[O] What is a good way to get some source blocks to inherit file local variables? lexical-binding specifically

[Grant Rettke]

Good evening,

I am working on an Org document. It is mostly Emacs Lisp source blocks.
I set `lexical-binding' to `t' in the Org document. My goal was that
when I entered source-block-buffers that they would inherit that
property. They don't. I wanted that setting to get inherited because the
document is tangled into Emacs-Lisp files that have the property set.

Emacs: `24.4.1'.

Org-Mode: `8.3.1'. Obtained from Git. Latest.

The init file looks like this:

✂✂
;; -*- lexical-binding: t -*- (setq load-prefer-newer t) (add-to-list
'load-path "~/src/org-mode/lisp") (add-to-list 'load-path
"~/src/org-mode/contrib/lisp") (setq org-list-allow-alphabetical t)
(require 'org) (setq org-babel-noweb-wrap-start "«") (setq
org-babel-noweb-wrap-end "»")
✂✂

I start it like this: `open /Applications/Emacs.app --args --quick
--load ~/src/help/.org-mode-ecm.emacs.el'

A file that I am working on for example follows:

# ✂✂
# -*- lexical-binding: t -*-

#+BEGIN_SRC emacs-lisp
lexical-binding
#+END_SRC

#+RESULTS:

# ✂✂

When I enter the source block and evaluate it with
`org-babel-execute-src-block' the result it is nil. That is consistent
with inspecting it's value.

What is a good way to get some source blocks to inherit file local
variables?

Sincerely,

gcr

Re: [O] [PATCH] Only use HTML5 fancy elements in HTML5

[Eric Abrahamsen]

Rasmus  writes:

> Hi,
>
> Eric Abrahamsen  writes:
>
>> Currently, if the global variable `org-html-html5-fancy' is t, some
>> elements of HTML export will use fancy elements even when not exporting
>> to HTML5 at all.
>>
>> Specifically, the TITLE of a document will be wrapped in  tags,
>> even when exporting to XHTML4. I ran into this while making some epub
>> files and the syntax checker barked at me.
>>
>> This patch fills out the check. There's growing redundancy in this file
>> now -- if it seems desirable to have a `org-html-html5-fancy-p' function
>> that encapsulates the paired checks, I'd be happy to provide that.
>
> Remind me, do we have a "non-fancy" HTML5 mode?
>
> I think it's better to introduce a new function to check if fancy HTML5.
> This would make it easier to adhere to the docstring of
> org-html-html5-fancy:
>
>  "This variable is ignored for anything other than HTML5 export"

Yup, this was the problem. We do have "non-fancy" HTML5: just HTML5
without the use of any of the new elements like  or , which
aren't currently handled right by all browsers. All the various options
make for some fiddly conditionals, but I think it's worth it.

Here's another patch with a new function.

Thanks!
Eric

>From d0150b8c34efb1086dd5b240b256b0cf1f053148 Mon Sep 17 00:00:00 2001
From: Eric Abrahamsen 
Date: Tue, 18 Aug 2015 08:42:35 +0800
Subject: [PATCH] Add function to better guard html5 exports

* lisp/ox-html.el (org-html-html5-fancy-p): New function. Check that
  we're exporting to HTML5, *and* that the user has requested fancy
  elements.
  (org-html--wrap-image, org-html-template, org-html-toc)
  (org-html-special-block): Use new function.
---
 lisp/ox-html.el | 20 +++-
 1 file changed, 11 insertions(+), 9 deletions(-)

diff --git a/lisp/ox-html.el b/lisp/ox-html.el
index bdcdeee..78c8e11 100644
--- a/lisp/ox-html.el
+++ b/lisp/ox-html.el
@@ -1473,6 +1473,10 @@ CSS classes, then this prefix can be very useful."
   (let ((dt (downcase (plist-get info :html-doctype
 	(member dt '("html5" "xhtml5" ""
 
+(defun org-html-html5-fancy-p (info)
+  (and (plist-get info :html-html5-fancy)
+   (org-html-html5-p info)))
+
 (defun org-html-close-tag (tag attr info)
   (concat "<" tag " " attr
 	  (if (org-html-xhtml-p info) " />" ">")))
@@ -1503,8 +1507,7 @@ attributes with a nil value will be omitted from the result."
 INFO is a plist used as a communication channel.  When optional
 arguments CAPTION and LABEL are given, use them for caption and
 \"id\" attribute."
-  (let ((html5-fancy (and (org-html-html5-p info)
-			  (plist-get info :html-html5-fancy
+  (let ((html5-fancy (org-html-html5-fancy-p info)))
 (format (if html5-fancy "\n%s%s\n"
 	  "\n%s%s\n")
 	;; ID.
@@ -1929,16 +1932,17 @@ holding export options."
;; Document title.
(when (plist-get info :with-title)
  (let ((title (plist-get info :title))
-	   (subtitle (plist-get info :subtitle)))
+	   (subtitle (plist-get info :subtitle))
+	   (html5-fancy (org-html-html5-fancy-p info)))
(when title
 	 (format
-	  (if (plist-get info :html-html5-fancy)
+	  (if html5-fancy
 	  "\n%s\n%s"
 	"%s%s\n")
 	  (org-export-data title info)
 	  (if subtitle
 	  (format
-	   (if (plist-get info :html-html5-fancy)
+	   (if html5-fancy
 		   "%s\n"
 		 "\n\n%s\n")
 	   (org-export-data subtitle info))
@@ -2133,8 +2137,7 @@ of contents as a string, or nil if it is empty."
 			 (org-html--toc-text toc-entries)
 			 "\n")))
 	(if scope toc
-	  (let ((outer-tag (if (and (org-html-html5-p info)
-(plist-get info :html-html5-fancy))
+	  (let ((outer-tag (if (org-html-html5-fancy-p info)
 			   "nav"
 			 "div")))
 	(concat (format "<%s id=\"table-of-contents\">\n" outer-tag)
@@ -3181,8 +3184,7 @@ CONTENTS holds the contents of the block.  INFO is a plist
 holding contextual information."
   (let* ((block-type (org-element-property :type special-block))
 	 (contents (or contents ""))
-	 (html5-fancy (and (org-html-html5-p info)
-			   (plist-get info :html-html5-fancy)
+	 (html5-fancy (and (org-html-html5-fancy-p info)
 			   (member block-type org-html-html5-elements)))
 	 (attributes (org-export-read-attribute :attr_html special-block)))
 (unless html5-fancy
-- 
2.5.0

Re: [O] current status of citation syntax discussion

[Joseph Vidal-Rosset]

Hi everybody,

Thanks to Eric's example (here :
https://lists.gnu.org/archive/html/emacs-orgmode/2014-01/msg01262.html ) I
have succeeded to use ox-bibtex.el. \cite{} in the org file works both for
html and latex.

Nevertheless, I wonder how to get for org-file the org citation syntax
[[cite: ]] instead of \cite{} when I choose a reference from my
references.bib file . Is it possible to change this point in order to get
the same org file than in Eric's example ?

Best wishes,

Jo.

2015-06-16 22:43 GMT+02:00 Nicolas Goaziou :

> Hello,
>
> Matt Price  writes:
>
> > Is the discussion stalled out then?  What would have to happen to move it
> > along?
>
> There is a "wip-cite" branch in the git repo with basic Org syntax for
> citations. We're mainly waiting for implementations making use of it, on
> both export and references management side.
>
>
> Regards,
>
> --
> Nicolas Goaziou
>
>