[O] org-mode and appointment notifications on Mac OS 10.8

[Sarah Bagby]

I've been looking for a way to get org-mode to push appointment notifications 
from my org-agenda to the Notification Center on Mac OS 10.8 (Mountain Lion).  
Thanks to Eloy Durán's terminal-notifier project 
(https://github.com/alloy/terminal-notifier), the code below seems to do the 
trick.  This is mostly hacked together from other people's approaches using 
different window functions:

http://emacs-fu.blogspot.com/2009/11/showing-pop-ups.html
http://article.gmane.org/gmane.emacs.orgmode/5271
http://article.gmane.org/gmane.emacs.orgmode/5806

I'm posting in the hopes that this will be useful to others, and would welcome 
any feedback.

Sarah Bagby

;

(require 'appt)
(setq appt-time-msg-list nil);; clear existing appt list
(setq appt-display-interval '10) ;; warn every 10 minutes from t - 
appt-message-warning-time
(setq
  appt-message-warning-time '10  ;; send first warning 10 minutes before 
appointment
  appt-display-mode-line nil ;; don't show in the modeline
  appt-display-format 'window)   ;; pass warnings to the designated window 
function
(appt-activate 1);; activate appointment notification
(display-time)   ;; activate time display

(org-agenda-to-appt) ;; generate the appt list from org agenda 
files on emacs launch
(run-at-time "24:01" 3600 'org-agenda-to-appt)   ;; update appt list 
hourly
(add-hook 'org-finalize-agenda-hook 'org-agenda-to-appt) ;; update appt list on 
agenda view

;; set up the call to terminal-notifier
(defvar my-notifier-path 
  
"~/terminal-notifier_1.4.2/terminal-notifier.app/Contents/MacOS/terminal-notifier")
  
(defun my-appt-send-notification (title msg)
  (shell-command (concat my-notifier-path " -message " msg " -title " title)))

;; designate the window function for my-appt-send-notification
(defun my-appt-display (min-to-app new-time msg)
  (my-appt-send-notification 
(format "'Appointment in %s minutes'" min-to-app);; passed to -title in 
terminal-notifier call
(format "'%s'" msg)));; passed to -message 
in terminal-notifier call
(setq appt-disp-window-function (function my-appt-display))

;


-
Sarah Bagby
Postdoctoral scientist, Valentine lab
Department of Earth Science / Marine Science Institute
Webb Hall
UC Santa Barbara
Santa Barbara, CA 93106
ba...@geol.ucsb.edu
-

Re: [O] orgstruct-mode with custom headline prefix

[Christopher Schmidt]

Christopher Schmidt  writes:
> I will push a fix ASAP.

I did that now.

d6f69f5 org.el: Use let instead of progv in org-run-like-in-org-mode
ea2d107 org.el: Declare orgstruct-mode

Christopher

Re: [O] [new exporter] workaround/replacement for org-export-as-html-batch

[Detlef Steuer]

On Tue, 12 Feb 2013 20:34:55 +0100
Nicolas Goaziou  wrote:

> Does `org-html-export-to-html' works as a replacement for
> `org-export-as-html-batch'?

Yes! Thank you so much!

Detlef

Re: [O] orgstruct-mode with custom headline prefix

[Sebastien Vauban]

Hi Christopher and Bastien,

Christopher Schmidt wrote:
> Christopher Schmidt  writes:
>> I will push a fix ASAP.
>
> I did that now.
>
> d6f69f5 org.el: Use let instead of progv in org-run-like-in-org-mode
> ea2d107 org.el: Declare orgstruct-mode

FYI, I still have the reported problem when composing an email:

Lisp nesting exceeds `max-lisp-eval-depth'

Org-mode version 7.9.3e (7.9.3e-1002-gd6f69f @ 
d:/Users/fni/Public/Repositories/org-mode/lisp/)

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] [BUG] (error "Lisp nesting exceeds `max-lisp-eval-depth'")

[Christopher Schmidt]

"Sebastien Vauban"  
writes:
> Since the last pull I made, I can't expand anymore BBDB aliases in
> Gnus...  because of Org!
> Debugger entered--Lisp error: (error "Lisp nesting exceeds 
> `max-lisp-eval-depth'")

It looks like this is orgstruct-mode and yas-snippet both hijacking the
TAB key and ultimately falling back to each other.  Could you please
give master + this patch a try?
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -8672,7 +8672,8 @@ should be checked in for a command to execute outside of tables."
  'item-body)))
 (org-run-like-in-org-mode ',fun)
 t))
-  (let ((binding (let ((orgstruct-mode)) (key-binding ,key
+  (let* ((orgstruct-mode)
+		 (binding (key-binding ,key)))
 (if (keymapp binding)
 (set-temporary-overlay-map binding)
   (call-interactively

Christopher

Re: [O] [BUG] (error "Lisp nesting exceeds `max-lisp-eval-depth'")

[Sebastien Vauban]

Hi Christopher,

Christopher Schmidt wrote:
> Sebastien Vauban writes:
>> Since the last pull I made, I can't expand anymore BBDB aliases in
>> Gnus...  because of Org!
>> Debugger entered--Lisp error: (error "Lisp nesting exceeds
>> max-lisp-eval-depth'")
>
> It looks like this is orgstruct-mode and yas-snippet both hijacking the
> TAB key and ultimately falling back to each other.  Could you please
> give master + this patch a try?
>
> --- a/lisp/org.el
> +++ b/lisp/org.el
> @@ -8672,7 +8672,8 @@ should be checked in for a command to execute outside 
> of tables."
>   'item-body)))
>  (org-run-like-in-org-mode ',fun)
>  t))
> -  (let ((binding (let ((orgstruct-mode)) (key-binding ,key
> +  (let* ((orgstruct-mode)
> +  (binding (key-binding ,key)))
>  (if (keymapp binding)
>  (set-temporary-overlay-map binding)
>(call-interactively

Well, it seems to yes. Thanks!

What's weird is that I applied the patch, and then did C-M-x with the cursor
in the function. I did test composing an email, and it still did not work.

I restarted Emacs to be really, really sure, and now it works!

So, I don't know what's bad in the above procedure (C-M-x of the fucntion),
but your patch works, yes.

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] OT, but not really: todays XKCD

[Bastien]

Hi Eric,

Eric S Fraga  writes:

> If there is a consensus on the list that I am going against some form of
> etiquette for this list, I am happy to change my settings.  I have no
> interest in annoying people!

Accepting standard use of Mail-Followup-To on this list is fine.

Let see if someone directly impacted complains one day.

For Gnus users who find your MFT confusing, there is this option:
(setq message-use-mail-followup-to nil)

Thanks,

-- 
 Bastien

Re: [O] [ANN] outorg.el -- reverse Org-Babel

[Bastien]

Hi Thorsten,

Thorsten Jolitz  writes:

> But I will try to refactor the whole thing so that it becomes immaterial
> if orgstruct-mode or outline-minor-mode is used (I assume there are
> equivalents for 'outline-regexp' and 'outline-level' in
> orgstruct-mode).

See `org-outline-regexp' and `org-outline-level'.

HTH,

-- 
 Bastien

Re: [O] double-width characters in tables

[Bastien]

Hi Eric,

Eric Abrahamsen  writes:

> Solving the problem then might mean just using `org-string-width'
> directly in the code, in the places where string width is currently
> calculated from text property values. I'll poke at it, and see how badly
> I break it.

Thanks for digging further -- if you can find a bug that doesn't
involve mixing languages (e.g. if users are inserting special but
common characters?), that'd even better!

-- 
 Bastien

Re: [O] Worg publishing issue

[Bastien]

Hi Nicolas,

Nicolas Goaziou  writes:

> Bastien  writes:
>
>> 2 problems, a trivial one and a let's-prepare-for-headache one:
>>
>> 1. `org-publish-org-to-html' does not exist in the new export/publish
>> libraries -- Nicolas, would that be enough to have aliases here
>> (from org-publish-org-to-html to org-html-publish-to-html)?  I
>> guess many people rely on thse org-publish-org-to* functions.
>
> Publishing functions have been moved into their respective back-end.
> That way, ox-publish.el doesn't have to know about every back-end
> defined.

Thanks -- so that's not a problem for Worg, which uses Org from the
maint branch for publishing.  I've just fixed the bug in maint that
prevented Worg from publishing correctly.

> It's not very clean, but you can probably define aliases in
> ox-publish.el, since real publishing functions should be autoloaded
> anyway. If you do so, I suggest to, at least, provide a deprecation
> notice.*

I don't plan to add those aliases, let's move forward and add the
deprecation notice in the 8.0 release announcement (and on Worg.)

Thanks,

-- 
 Bastien

Re: [O] [ANN] outorg.el -- reverse Org-Babel

[Thorsten Jolitz]

Bastien  writes:

Hi Bastien,

> Note that both your libraries (supporting some Org syntax in
> comments) are a perfect match for Christopher recent chance
> in master, which allows a more powerful orgstruct-mode in
> those files -- with folding etc.  If you didn't, have a look:
>
>   C-h v orgstruct-heading-prefix-regexp RET

for equivalence with outline-minor-mode, one would need 

,
| orgstruct-heading-prefix-regexp
| orgstruct-heading-prefix-level
`

just like: 

,---
| outline-regexp is a variable defined in `outline.el'.
| 
| Regular expression to match the beginning of a heading.
| Any line whose beginning matches this regexp is considered to start a heading.
| Note that Outline mode only checks this regexp at the start of a line,
| so the regexp need not (and usually does not) start with `^'.
| The recommended way to set this is with a Local Variables: list
| in the file it applies to.  See also `outline-heading-end-regexp'.
`---

,
| outline-level is a variable defined in `outline.el'.
| 
| *Function of no args to compute a header's nesting level in an outline.
| It can assume point is at the beginning of a header line and that the match
| data reflects the `outline-regexp'.
`

on the other hand:

,-
| (define-derived-mode org-mode outline-mode "Org"
| [...]
|   (org-set-local 'outline-regexp org-outline-regexp)
|   (org-set-local 'outline-level 'org-outline-level) ...)
`-

I'm not sure if I really understand orgstruct-mode, but it seems to me
that when orgstruct-mode is active in a (e.g. elisp) buffer, all outline
functions and vars are available, and so are org-outline-regexp and
org-outline-level. 

Then a library like outorg could use outline functionality in its
functions and it would work no matter if the buffer is in
outline-minor-mode or in orgstruct-mode. The only change necesary would
be to set outline-regexp and outline-level conditionally on the
minor-mode active. 

Or why not use outline-regexp and outline-level directly, like org.el
does in some places: 

,---
| 6624:(if (re-search-forward (concat "^" outline-regexp) nil t)
`---

,-
| 36 matches for "[^-]outline-level" in buffer: org.el
`-

I'm not really sure how much of Org-mode and Outline is available when
orgstruct is loaded, and if and why there is a need for
'orgstruct-heading-prefix-regexp' - couldn't orgstruct just set a
buffer-local 'outline-regexp' instead? Some enlightment is welcome. 

-- 
cheers,
Thorsten
 

[O] Bug in orgstruct++?

[Thorsten Jolitz]

Hi List, 

after upgrading to the newest git-version just moments ago, I had to
disable orgstruct++ in message-mode because of this error: 

,
| org-defkey: Key sequence C-c @ C-> starts with non-prefix key C-c @
`

Is that a bug or somehow related to my redefinition of the
outline-minor-mode prefix from 'C-c @' to 'C-c'?

-- 
cheers,
Thorsten

Re: [O] [ANN] outorg.el -- reverse Org-Babel

[Thorsten Jolitz]

Bastien  writes:

Hi Bastien,

>> But I will try to refactor the whole thing so that it becomes immaterial
>> if orgstruct-mode or outline-minor-mode is used (I assume there are
>> equivalents for 'outline-regexp' and 'outline-level' in
>> orgstruct-mode).
>
> See `org-outline-regexp' and `org-outline-level'.

just posted a question with regards to this ...

-- 
cheers,
Thorsten

Re: [O] org-agenda-show-log, org-timeline bugs

[Bastien]

Hi Derek,

Derek Upham  writes:

> Can someone please verify these bugs?  Thanks.

Sorry, no special effort is made to fix bugs in org-timeline because
its future is uncertain: there is significant overlap between this
feature from the early days of Org, and the general agenda views
mechanism.

We'll make a decision about org-timeline before releasing Org 8.0: 
if it stays, let's fix it.  If it goes, let's forget it!

Thanks,

PS: Patches are always welcome as an encouragement to keep it.

-- 
 Bastien

Re: [O] [PATCH] Re: double-width characters in tables

[Bastien]

Hi Eric,

Eric Abrahamsen  writes:

> - l (max 1 (- (match-end 0) (match-beginning 0) 3))
> + l (max 1
> +(- (org-string-width
> +(buffer-substring
> + (match-end 0) (match-beginning 0))) 3))

(Why not just (org-string-width (match-string 0))?)

Let me know when you're done with extensive testing for this!

Thanks,

-- 
 Bastien

[O] Bug: [BUG] Interference of radio targets and external links [7.9.3e (7.9.3e-956-g3943be.dirty @ /home/vdyadov/Work/Tools/emacs/org-mode/lisp/)]

[Дядов Васил Стоянов]

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.


Hi!

I've an issue with radio targets and ordinary external links.

#+begin_src org
#+ATTR_HTML: border="1" frame="border" style="max-width:50%;"
| / | <>   | <> | <>   |
|   | Test | Description| Source  file |
|---+--++--|
|   | <<>>   | Inverse DCT| [[file:test/idct.c][idct.c]] |
|---+--++--|
#+end_src

In this case external link "[[file:test/idct.c][idct.c]]" in html file
looks like: .c


Emacs  : GNU Emacs 24.2.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.18.9)
 of 2012-12-25 on canopus-pc.elvees.com
Package: Org-mode version 7.9.3e (7.9.3e-956-g3943be.dirty @ 
/home/vdyadov/Work/Tools/emacs/org-mode/lisp/)

Re: [O] Still Wishing for Snooze

[Samuel Loury]

Bastien  writes:

> Point well taken -- this is now what adding "--2d" does: use a
> temporary delay that will not be taken into account for dates later
> than the next repeater, and that will be deleted when a repeating
> task is marked as done.  Thanks for suggesting this.

Thanks for the --2d feature!

May be I should also consider sending you a cheesecake ;-).

-- 
Konubinix
GPG Key: 7439106A
Fingerprint: 5993 BE7A DA65 E2D9 06CE  5C36 75D2 3CED 7439 106A


pgpCNksQNAlTr.pgp
Description: PGP signature

Re: [O] [ANN] outorg.el -- reverse Org-Babel

[Bastien]

Hi Thorsten,

Thorsten Jolitz  writes:

> I'm not sure I fully understand this, but working with 'org-id' would
> definitely have been another option. Maybe even in combination with
> dynamic blocks?

Instead of just supporting new special links in non-org buffers,
maybe we can try to supports links in general.

But at the same time, we don't want everybody on Earth to end up
with strings like [[http://orgmode.org][links]] in the source code
they write/read.  I'd really think twice before implementing such
features.

2 cts of course,

-- 
 Bastien

Re: [O] Still Wishing for Snooze

[Bastien]

Samuel Loury  writes:

> May be I should also consider sending you a cheesecake ;-)

Well, cheesecake don't travel very well through the Atlantic,
a postcard would do!  :)

-- 
 Bastien

Re: [O] [BUG] (error "Lisp nesting exceeds `max-lisp-eval-depth'")

[Christopher Schmidt]

"Sebastien Vauban"  
writes:
> What's weird is that I applied the patch, and then did C-M-x with the
> cursor in the function. I did test composing an email, and it still
> did not work.
>
> I restarted Emacs to be really, really sure, and now it works!
>
> So, I don't know what's bad in the above procedure (C-M-x of the
> fucntion), but your patch works, yes.

That is expected.  The function is only executed the very first time you
enable orgstruct\(++\)-mode.

orgstruct-mode is an ugly hack.  So is yasnippet.  There is no fix for
this problem, just a workaround that can introduce other issues in
somewhat rare and obscure corner cases.

I applied the patch.

7c27e57 org.el: Disable orgstruct-mode when falling back to original command

Christopher

[O] [PATCH] Re: double-width characters in tables

[Eric Abrahamsen]

Eric Abrahamsen  writes:

> Achim Gratz  writes:
>
>> Eric Abrahamsen writes:
>>> Yes, org-string-width eventually calls string-width, so that behaves
>>> "correctly" as far as it goes
[...]

And more, this time to prevent errors when using column-narrowing
cookies on columns containing peculiar-width strings. It's still going
to look weird, often as not, but this will at least prevent blowups.

I'm providing two possible patches. One is a one-liner that does the
trick but produces ugly results. The other goes a wee bit overboard, but
looks a little better. I offer either, or neither, for consideration.

Eric

>From ccf294f9dad0b81240b8f1a0051cecfddd47d1c4 Mon Sep 17 00:00:00 2001
From: Eric Abrahamsen 
Date: Wed, 13 Feb 2013 16:46:33 +0800
Subject: [PATCH] Make table column narrowing play nice with variable-width
 strings

---
 lisp/org-table.el | 19 ++-
 1 file changed, 14 insertions(+), 5 deletions(-)

diff --git a/lisp/org-table.el b/lisp/org-table.el
index 3f276f8..d79b650 100644
--- a/lisp/org-table.el
+++ b/lisp/org-table.el
@@ -765,7 +765,7 @@ When nil, simply write \"#ERROR\" in corrupted fields.")
 	 (hfmt1 (concat
 		 (make-string sp2 ?-) "%s" (make-string sp1 ?-) "+"))
 	 emptystrings links dates emph raise narrow
-	 falign falign1 fmax f1 len c e space)
+	 falign falign1 fmax f1 f2 len c e space)
 (untabify beg end)
 (remove-text-properties beg end '(org-cwidth t org-dwidth t display t))
 ;; Check if we have links or dates
@@ -850,10 +850,19 @@ When nil, simply write \"#ERROR\" in corrupted fields.")
 		  (unless (> f1 1)
 		(error "Cannot narrow field starting with wide link \"%s\""
 			   (match-string 0 xx)))
-		  (add-text-properties f1 (length xx) (list 'org-cwidth t) xx)
-		  (add-text-properties (- f1 2) f1
-   (list 'display org-narrow-column-arrow)
-   xx)
+		  (setq f2 (length xx))
+		  (if (= (org-string-width xx)
+			 f2)
+		  (setq f2 f1)
+		(setq f2 1)
+		(while (< (org-string-width (substring xx 0 f2))
+			  f1)
+		  (setq f2 (1+ f2
+		  (add-text-properties f2 (length xx) (list 'org-cwidth t) xx)
+		  (add-text-properties (if (>= (string-width (substring xx (1- f2) f2)) 2)
+	   (1- f2) (- f2 2)) f2
+	   (list 'display org-narrow-column-arrow)
+	   xx)
   ;; Get the maximum width for each column
   (push (apply 'max (or fmax 1) 1 (mapcar 'org-string-width column))
 	lengths)
-- 
1.8.1.3

>From 319931ba76fc3ce5b8157f131d7c71c18f4c5d60 Mon Sep 17 00:00:00 2001
From: Eric Abrahamsen 
Date: Wed, 13 Feb 2013 15:07:59 +0800
Subject: [PATCH] Prevent errors with table column narrowing and variable-width
 strings

---
 lisp/org-table.el | 1 +
 1 file changed, 1 insertion(+)

diff --git a/lisp/org-table.el b/lisp/org-table.el
index 3f276f8..6fbff7a 100644
--- a/lisp/org-table.el
+++ b/lisp/org-table.el
@@ -850,6 +850,7 @@ When nil, simply write \"#ERROR\" in corrupted fields.")
 		  (unless (> f1 1)
 		(error "Cannot narrow field starting with wide link \"%s\""
 			   (match-string 0 xx)))
+		  (setq f1 (round (* (/ (float (length xx)) (org-string-width xx)) f1)))
 		  (add-text-properties f1 (length xx) (list 'org-cwidth t) xx)
 		  (add-text-properties (- f1 2) f1
    (list 'display org-narrow-column-arrow)
-- 
1.8.1.3

Re: [O] Critic markup

[Alan Schmitt]

Alan L Tyree writes:

> A much older suggestion for editing text which is particularly suitable 
> for electronic text:
>
> http://www.mpi-nf.mpg.de~hitoshi/otherprojects/manued/index.shtml
>
> http://www.mpi-inf.mpg.de/~hitoshi/otherprojects/manued/FAQ.shtml
>
> And there is an emacs mode for it: manued.el

Thanks, this is quite nice. I found where the code lives now:
https://github.com/yamauchih/manued

It would be great if there was a way to add comments as well without
repeating the text. It seems the only options are:

blah blah blah [/; comment with no indication on what]
blah blah [blah/blah; I put context, but I need to repeat the text]

Thanks a lot for the link!

Alan

Re: [O] Bug in orgstruct++?

[Christopher Schmidt]

Thorsten Jolitz  writes:
> after upgrading to the newest git-version just moments ago, I had to
> disable orgstruct++ in message-mode because of this error:
>
> ,
> | org-defkey: Key sequence C-c @ C-> starts with non-prefix key C-c @
> `

Fixed in master.

e7403d6 org.el: Ignore errors when bindings keys in orgstruct-setup

Christopher

Re: [O] [BUG] (error "Lisp nesting exceeds `max-lisp-eval-depth'")

[Sebastien Vauban]

Hi Christopher,

Christopher Schmidt wrote:
> "Sebastien Vauban"  writes:
>> What's weird is that I applied the patch, and then did C-M-x with the
>> cursor in the function. I did test composing an email, and it still
>> did not work.
>>
>> I restarted Emacs to be really, really sure, and now it works!
>>
>> So, I don't know what's bad in the above procedure (C-M-x of the
>> fucntion), but your patch works, yes.
>
> That is expected.  The function is only executed the very first time you
> enable orgstruct\(++\)-mode.
>
> orgstruct-mode is an ugly hack.  So is yasnippet.  There is no fix for
> this problem, just a workaround that can introduce other issues in
> somewhat rare and obscure corner cases.
>
> I applied the patch.
>
> 7c27e57 org.el: Disable orgstruct-mode when falling back to original 
> command

Thanks for the explanation to the mystery, and for the patch.

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] [PATCH] Re: double-width characters in tables

[Eric Abrahamsen]

Bastien  writes:

> Hi Eric,
>
> Eric Abrahamsen  writes:
>
>> -l (max 1 (- (match-end 0) (match-beginning 0) 3))
>> +l (max 1
>> +   (- (org-string-width
>> +   (buffer-substring
>> +(match-end 0) (match-beginning 0))) 3))
>
> (Why not just (org-string-width (match-string 0))?)
>
> Let me know when you're done with extensive testing for this!

I think the reason I went with buffer-substring is that it will *fix*
messed up justification. (match-string 0) will not mess up the
justification if it's already correct, but it won't fix it if it isn't.

Actually, shortly after sending that patch I moved to using
buffer-substring-no-properties, which has the added benefit that fields
with links or other types of hidden text will justify correctly. Unless
I'm mistaken, putting links in table fields will currently result in
too-short justification as handled by org-table-justify-field-maybe (as
always, a full re-align with org-table-align fixes things). Unless the
buffer-substring call is particularly expensive, I think it's worth it.

Re testing: apart from mixing scripts and languages in one field, what
else should be tested? You mentioned cleaning up other problems while
we're at it -- does anyone have anything outstanding?

Inevitably (I think), none of this works when the wrong typeface is
being used for particular characters. I have no specifications for
Cyrillic, for example, which means my system renders it in with a
Chinese typeface, resulting in double-wide glyphs for characters that
should be single-width, and bad table justification. I think this has to
be addressed by the user.

E

Re: [O] new exporter fails to output footnotes?

[Nicolas Goaziou]

Samuel Wales  writes:

> Thank you.  Confirmed that footnotes are included in HTML now.
>
> They are missing from plain text export.

Fixed too.

> In HTML, how do you control the hlevel of the footnotes header?

See `org-html-footnotes-section'.

> Also, there is a formatting issue with footnotes.  Here they are in w3m:
>
> ===
>
> ^ They became popular in the silence=death era.
> 1
>   This image by Jock Cooper is licensed under a Creative
> ^ Commons Attribution-Noncommercial 3.0 United States
> 2 License.
>
> ^ I didn't look up the types of self-similarity in
> 3 fractals.
>
>   This image is protected by a True Scottish copyright:
> ^ Creative Commons, Attribution — Noncommercial —
> 4 Share-alike 2.5 UK: Scotland.
>
> ^ Creative Commons Attribution-Share Alike 3.0 Unported
> 5
> ^ "Cur CUD brih sure" I ween.
> 6
>
> ===
>
> A slightly different formatting issue occurs in Firefox by default,
> but copy and paste might not depict it.

I cannot help you much at the moment, as I don't know well the HTML
back-end and I'm not sure what a correct fix for this would be.

Anyway, if you send the correct HTML that should be generated, I will
fix it.


Regards,

-- 
Nicolas Goaziou

Re: [O] latex exporter: different itemize environment

[Nicolas Goaziou]

Hello,

Andreas Leha  writes:

> Hi all (and Nicolas),
>
> from =org-e-latex.el= (I have to upgrade - I know):
> ,
> | ;; Plain lists accept two optional attributes: `:environment' and
> | ;; `:options'.  The first one allows to use a non-standard environment
> | ;; (i.e. "inparaenum").  The second one allows to specify optional
> | ;; arguments for that environment (square brackets are not mandatory).
> `
>
> I can not make the :enviroment switch work.
>
> Following is a small presentation with a non-indented version of
> itemize.  But when I export it, I still get an \begin{itemize} when
> instead I'd like \begin{nonindentlist}.
>
> What am I missing?

[...]

>#+ATTR_LATEX: :environment nonindentlist
>- some
>- bullet
>- points

It should be #+attr_beamer: :environment nonindentlist since this
property is defined in Beamer back-end's documentation.

Since arguments are the same and beamer back-end is derived from latex
anyway, lists should now accept both, though.


Regards,

-- 
Nicolas Goaziou

Re: [O] [new exporter] strange behaviour and a question for beamer export

[Nicolas Goaziou]

Hello,

Eric S Fraga  writes:

> It would appear, if I understand the documentation in ox-beamer.el
> correctly, that an ignoreheading block environment is incompatible with
> a column specification.  If this is so, it would be nice if the exporter
> would indicate an error of some sort or if the beamer minor mode would
> catch this; it might not be easy to do the latter, mind you.

Your understanding is correct. But, I see no ambiguity about the
relation between "ignoreheading" and "columns" in the documentation (it
is written that an "ignoreheading" explicitly closes a "columns"
environment)

On a related topic, I'd like to define some behaviour for combinations
like "ignoreheading + BEAMER_act". Hence:

--8<---cut here---start->8---
* Headline :ignoreheading:
  :PROPERTIES:
  :BEAMER_env: ignoreheading
  :BEAMER_act: 2-
  :END:

  Contents
--8<---cut here---end--->8---

should make contents appear outside of a (visible) block, but only from
the second frame. This isn't the case actually. I'm not sure about what
environment to use for that.

> Thanks and sorry again for all the noise.  My presentation is now ready
> in all its glory ;-)

Great.


Regards,

-- 
Nicolas Goaziou

[O] org-end-of-line deactivating region?

[Eric Abrahamsen]

Has anyone noticed this? With emacs -Q, the latest Org, and
org-special-ctrl-a/e set to t, activating the region and then hitting
C-e org-end-of-line deactivates the region. Am I dreaming?

E

Re: [O] Modifying the exporter

[Nicolas Goaziou]

Florian Beck  writes:

> Ok, I took some time to extract a minimal example. It works fine, but
> on a very low level (see below).
>
> Again, the goal is to add an optional argument to sectioning command.
> The best way I could come up with is this (I omit the
> `fb/org-export-pdf' function):
>
> #+BEGIN_SRC emacs-lisp
> (defun fb/org-export-modify-headline (headline string)
>   (if (string-match
>(rx
>   string-start "\\"
>   (group-n 1 (0+ "sub"))
>   (group-n 2 (or "part" "chapter" "section" "paragraph"))
>   (group-n 3 (zero-or-one "\*"))
>   "{" (group-n 4 (minimal-match (0+ (not (any "}") "}")
>string)
>   (let* ((level (match-string 1 string))
>(type (match-string 2 string))
>(stars (match-string 3 string))
>(title (match-string 4 string))
>(toc-title (org-element-property :toc-title headline))
>(new-hl
> (format "\\%s%s%s%s{%s}"
> (or level "")
> type
> (or stars "")
> (if toc-title (format "[%s]" toc-title) "")
> title)))
>   (replace-match new-hl t t string 0))
> string))

Why don't you simply replace (or add, if needed) optional argument from
sectioning command with `replace-regexp-in-string' instead of building
the whole string again? Like the following (untested):

#+begin_src emacs-lisp
(defun fb/org-latex-headline (headline contents info)
(let ((original-hl (org-export-with-backend 'latex headline contents info))
  (toc-title (org-element-property :toc-title headline)))
  (cond ((not toc-title) original-hl)
((string-match "\\`\\.*?\\*?\\[\\([^]]\\)\\]" original-hl)
 (replace-match toc-title nil nil original-hl 1))
(t (replace-regexp-in-string
"\\`\\.*?\\*?" (concat "\\&" toc-title) original-hl)
#+end_src

> As you can see, I pull apart the string and then put it back together.
> (Relatively straightforward in this case, much more involved for, say,
> links.)

Writing translators for headlines links and tables is usually a major
undertaking when creating a new back-end. That's why there are so many
tools to operate on these elements in ox.el.

Anyway, this is not bad, as you forked a 3k locs back-end with about 30
locs.

> In a perfect world, I would have access to these elements and the format
> string, so I could either modify them before calling
> `org-export-with-backend' or assemble the string myself.

In your perfect world, there would be billions of variables, depending
on the element, the back-end and the task. Customization is still
important, so I offer generic tools when variables are not enough.

Note that I might implement this feature at one point, but I still have
to think about its specifications.


Regards,

-- 
Nicolas Goaziou

Re: [O] BUG: coderef labels not stripped when tangling

[Bastien]

Hi Michael,

Michael Alan Dorman  writes:

> Using Org-mode to write in a literate style is a lot of fun.  When I
> read about coderef labels, they seemed likely to make it even better.
>
> The only problem is that they aren't stripped during tangling. If you
> tangle this:
>
> #+BEGIN_SRC sh -n -r :noweb tangle :shebang #!/bin/sh :tangle tangle-test.sh
> echo "Working" (ref:working) 
> #+END_SRC
>
> You end up with:
>
> #!/bin/sh
>
> echo "Working" (ref:working)
>
> That seems like a bug.

Indeed.  This show now be fixed (both in maint and master).
Please let us know if not.

Thanks a lot for reporting this nasty bug!

-- 
 Bastien

Re: [O] [PATCH] Fix uncaught error when trying to open a link at point

[Bastien]

Hi Samuel,

Samuel Loury  writes:

> It adjusts org-open-at-point to have plain links handled the same way
> bracket links are. It allows plain links to be followed if the cursor is
> before the link while still on the same line.

I applied a slightly modified version of your patch, condensing
comments.  See the change here:

http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=9964d8

> I also got rid of dangling parenthesis as suggested by
> Nicolas. Personally, I think it is easier to read with dangling
> parens. Could you explain what is wrong with them?

It's easy to allow oneself to have one or two dangling parentheses
when it clarifies code reading, but when you start using dangling
parentheses, it's hard to know where to stop... in any case, more
of a matter of convention + taste.

Thanks,

-- 
 Bastien

Re: [O] [PATCH] Add `org-reverse-string'

[Bastien]

Hi Daimrod,

Daimrod  writes:

> Eric Schulte  writes:
>
>> This patch looks fine to me, although you'll need to add a
>> `declare-function' call to the top of ob-core.el (and maybe to org-id as
>> well) or the compiler will complain.
>
> I've added a `declare-function' call to `ob-core.el' but I think I don't
> need to add it to `org-id.el' because it already require `org.el'.
>
> Thanks for taking time to review this patch.

I've applied this patch, thanks!

-- 
 Bastien

Re: [O] format of the ID property in the new HTML exporter

[Bastien]

Hi Florian,

Florian Beck  writes:

> Yes. Why do you need the assert? It only seems to be there to make my
> life more difficult.

I've remove the (assert ...) sexp, which was too strict, I agree.

Thanks,

-- 
 Bastien

Re: [O] org-end-of-line deactivating region?

[Bastien]

Hi Eric,

Eric Abrahamsen  writes:

> Has anyone noticed this? With emacs -Q, the latest Org, and
> org-special-ctrl-a/e set to t, activating the region and then hitting
> C-e org-end-of-line deactivates the region. Am I dreaming?

I can't reproduce this.  ECM?

-- 
 Bastien

Re: [O] Org interpreting multiple ^{*} instances as bold in LaTeX beamer export

[Bastien]

Hi John,

John Hendy  writes:

> I just wanted an asterisk to put a little footnote for two items in a
> longer list and noticed that it shifted the whole slide up. Same for
> regular LaTeX document export. Seems like it only happens if the two
> bullets are consecutive.

The last component of `org-emphasis-regexp-components' is the number
of newlines allowed when emphasizing.  This is 1 by default, meaning
that you cannot use markup on more than two consecutive lines.

In any case, you can simply use another character than "*" for the
time being, we are working on this part of the code.  The plan is
to allow to deactivate some markup based on a variable.

Thanks,

-- 
 Bastien

[O] ending table data entry

[Jude DaShiell]

If an emacs-orgmode document is written that starts with text, then a 
table, then text comes after the table, what should be put in the document 
to let emacs-orgmode know we're back to text on this and following lines 
until another table is started?

---
jude 
Remember Microsoft didn't write Tiger 10.4 or any of its successors.

Re: [O] Fwd: Re: Bug? in texinfo exporter

[Thomas S. Dye]

Nicolas Goaziou  writes:

>> (add-to-list 'org-export-snippet-translation-alist
>>  '("info" . "e-texinfo"))
>
> Note: this should be '("info" . "texinfo") as the back-end has been
> renamed.

Good eye.  Thanks.

>> Here is the makeinfo output:
>>
>> poto:orgmanual dk$ makeinfo --force org-texi-link.texi
>> /Users/dk/org/orgmanual//org-texi-link.texi:55: Cross reference to
>> nonexistent node
>> A-long-headline-that-typically-breaks-across-lines-with-M-q'
>> (perhaps incorrect sectioning?).
>>
>> Note the hyphens between the words of the headline/link.
>
> The bug should be fixed now. Could you confirm it?

Fixed.  Thanks.

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

Re: [O] org-mode and appointment notifications on Mac OS 10.8

[Bastien]

Hi Sarah,

Sarah Bagby  writes:

> I'm posting in the hopes that this will be useful to others, and
> would welcome any feedback.

I'm not using Mac OS but I guess this will be useful, I just posted
a link to this email on http://orgmode.org/worg/org-hacks.html

Thanks!

-- 
 Bastien

Re: [O] ocaml babel no longer works?

[Eric Schulte]

Alan Schmitt  writes:

> Hello,
>
> Eric Schulte writes:
>
>> Thanks for looking into this.  I've applied a patch to ob-ocaml.el which
>> should handle the two different tuareg execution functions.
>
> Thanks a lot.
>
> About the thing "getting stuck", I made some progress. My error was that
> I did not add ";;" at the end of my ocaml phrase, which resulted in an
> error in the toplevel:
>
> #+begin_quote
> Objective Caml version 3.12.1
>
> # let x = 2 in x
> "org-babel-ocaml-eoe";;
>   Characters 13-14:
>   let x = 2 in x
>^
> Error: This expression is not a function; it cannot be applied
> #+end_quote
>
> As you see, it's trying to apply the 'x' to the "oeo" thing. My guess is
> that babel waits until seeing this special string before sending the
> result back. By the way, this allows for some fun things, like this:
>
> #+BEGIN_SRC ocaml
> let f x = () in f
> #+END_SRC
>
> make babel stuck because the interpreter is in this state:
>
> #+begin_quote
> # let f x = () in f
> "org-babel-ocaml-eoe";;
>   - : unit = ()
> #+end_quote
>
> So I have a suggestion and two feature requests.
>
> The suggestion: instead of appending '"org-babel-ocaml-eoe";;' to the
> code, how simply put ';;' (which will make sure everything is flushed)
> then detect the toplevel is done by seeing the string '# ' at the
> beginning of the line? Would there be an issue with the fact that this
> line does not have a newline? If so, an alternative suggestion would be
> to use the longer ';; "org-babel-ocaml-eoe";;' which makes sure the
> phrase in the input won't interact with the marker.
>

You can customize the `org-babel-ocaml-eoe-output' and
`org-babel-ocaml-eoe-indicator' variables so that they match the above.
If this proves generally useful then I'd be happy to admit this change
to the core.

>
> The first feature requests: if there is an error, could it be parsed?
> (It probably always start with 'Error: '). Then the error could be put
> in the result block, instead of waiting for the marker that will never
> appear.
>

In `org-babel-execute:ocaml' first the `raw' variable is assigned to the
raw output of the ocaml session, it is then parsed into the `clean'
variable.  Between these two steps it should be possible to check for an
error string and possibly raise an error with
`org-babel-eval-error-notify'.

>
> The second feature request: I want to use this for my ocaml lab classes
> (I'm thinking of giving them an org file they have to complete by
> writing the caml code). Could it be possible to have an option for the
> full output of the compiler (and not just the result) to be printed? I
> see it does it when it does not recognize the type of the output. So I
> guess such an option would be applied to either
> org-babel-ocaml-parse-output or the place where it's called.
>

I would think adding a ":results verbatim" header argument would
suffice, but perhaps this is not the case.

>
> Thanks a lot for any suggestion as how to implement this. I think I see
> how to do the second one (except I don't know how to add a configuration
> variable to toggle it). I have no idea about the first one, though.
>

I hope these pointers are useful.  I apologize for not being able to
take a look at this myself, but I'm simply too busy.  ob-ocaml could
certainly use some attention, and I hope that if you do make
improvements you consider contributing them back to Org-mode.  In
general other more mature language modes should serve as a guide to most
implementation questions.

Cheers,

>
> Alan

-- 
Eric Schulte
http://cs.unm.edu/~eschulte

Re: [O] BUG: coderef labels not stripped when tangling

[Michael Alan Dorman]

Bastien,

> Indeed.  This show now be fixed (both in maint and master).
> Please let us know if not.

Thanks so much for this and all the work you do on org.  I've finally
taken the plunge to learn emacs lisp, so perhaps before long I'll be
able to contribute as well. ;)

Mike.

Re: [O] Problem to export an orgmode file to pdf

[Bastien]

Hi Steve,

"Steve Prud'Homme"  writes:

> I have a problem. When i try to export my orgmode file de pdf c-c c-e p
> i have this message and no pdf file, what can i do to resolve the
> problem.

What version of Emacs/Org are you using?

-- 
 Bastien

[O] Anchors in texinfo export

[Thomas S. Dye]

Aloha all,

Currently, the texinfo exporter translates a dedicated target in a comment:

# <>

to this:

@c <>

I was expecting to see a texinfo anchor:

@anchor{x-export-to-odt}

There are a handful of these dedicated target comments cum anchors in the Org
mode manual. I believe all of them are in places where it would be easy
to replace them with links directly to the corresponding headline/node.

Should I edit them away? Or, are dedicated target comments/anchors
something the texinfo exporter should handle?

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

Re: [O] Macro expansion in new exporter

[Nicolas Goaziou]

tftor...@tftorrey.com (T.F. Torrey) writes:

> 1. You wrote before that macros were scaled back because what they did
> could be done by babel.  Is that really a good reason for removing
> functionality?  Everything that Org does could be done in other tools,
> and yet ... we have Org.

Macros were scaled down because the parser has to be able to know when
it looks at one of them. This limits the places where a macro can be
found. For example, it doesn't make much sense to expect a macro to be
found in an example block.

But scaling down macros made some of its features disappear. Since Babel
code could provide them anyway, it generated no real regression.

To sum it up, they were not downgraded because of Babel, but if Babel
hadn't been there, this wouldn't have happened.

> 2. You wrote to Carsten that macros could no longer contain newlines.
> That seems like an arbitrary limitation.  Is it?

In the parser, there's a difference between objects and elements.
Distinction is made clear in the comments lines of "org-element.el". To
put it simply, objects cannot contain blank lines.

Macros are objects. If I allow a newline in a macro, I allow two and
therefore a blank line. For example a macro within a paragraph could
potentially split it into two paragraphs. In this case, there would be
a mismatch between what the user can see in the buffer, and what will
happen during export.

Babel code already has got this privilege (of breaking structure of the
document). During alpha-test phase, bugs were reported because of
unanticipated discrepancies between Babel code in original buffer and
results in export buffer.

Allowing macros to do the same would be asking for more trouble.

> 3. Is there really a reason why macro expansion is limited to a few
> keywords rather than all?  Who would that trip up?  Ditto for verbatim
> and code emphasis.

Most keywords are simple key and values couples. The parser mustn't look
into the values, as it may find constructs that do not exist.

On the other hand some selected keywords have to be parsed, because
their value is really Org data. They are defined in "org-element.el".
See `org-element-document-properties' and `org-element-parsed-keywords'
for an exhaustive list.

Verbatim and code emphasis contents are never parsed, by definition.

> 4. Given that macro values are easy to find in the source document, and
> unexpanded macros are easy to find in the output document, couldn't I
> just add a filter to the exporter to find and expand any unexpanded
> macros (and lingering newline indicators)?  Is there an easy method for
> adding such a filter?

It may be possible, although very hackish. Functions in filters are, at
the moment, called from the export buffer. So you can probably read
macro definitions there. I think a proper filter to use for that would
be `org-export-filter-final-output-functions'.

I still strongly suggest to use Babel instead.

> 5. Actually, why do macros need to be an exporter problem at all?
> Couldn't the macro functionality be put into a separate package that
> used hooks and filters to connect itself into the export routine and the
> various back-ends (if even necessary)?  Then macros could be made to do
> interesting things without burdening the export engine (and its
> maintainer) at all.

Macros are an exporter problem, albeit a limited one, because their
expansion happens during the export process. Also, some macros are very
export oriented and have to be handled at the export framework level
(e.g. "{{{author}}}"). Though, an export back-end actually never sees
any macro, as these are expanded before its translator functions are
called.

Most of the macro code lives in org.el, and will probably be moved into
a separate library. Again, their limitations come from "org-element.el",
not "ox.el". Parsing them means "no crazy stuff allowed". For crazy
stuff, look towards Babel.


Regards,

-- 
Nicolas Goaziou

Re: [O] [PATCH] Fix uncaught error when trying to open a link at point

[Samuel Loury]

Hi,
Bastien  writes:

>> It adjusts org-open-at-point to have plain links handled the same way
>> bracket links are. It allows plain links to be followed if the cursor is
>> before the link while still on the same line.

By the way, the documentation of org-open-at-point says:

╭
│ If there is no link at point, this function will search forward up to
│ the end of the current line.
╰

Then the patch not only makes the behavior consistent but it makes the
implementation do what the documentation says.

>
> I applied a slightly modified version of your patch, condensing
> comments.  See the change here:
>
> http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=9964d8
>

I like it. It passes the tests and looks good for me.

> Thanks,

I am sorry for not sending the full patch myself: I am still waiting for
the documents indicating I can contribute to emacs.

-- 
Konubinix
GPG Key: 7439106A
Fingerprint: 5993 BE7A DA65 E2D9 06CE  5C36 75D2 3CED 7439 106A


pgphwsxkg8Xly.pgp
Description: PGP signature

Re: [O] Anchors in texinfo export

[Nicolas Goaziou]

Hello,

t...@tsdye.com (Thomas S. Dye) writes:

> Currently, the texinfo exporter translates a dedicated target in a comment:
>
> # <>

This isn't a target. This is a comment that contains some text looking
like Org syntax.

> to this:
>
> @c <>
>
> I was expecting to see a texinfo anchor:
>
> @anchor{x-export-to-odt}
>
> There are a handful of these dedicated target comments cum anchors in the Org
> mode manual. I believe all of them are in places where it would be easy
> to replace them with links directly to the corresponding headline/node.
>
> Should I edit them away? Or, are dedicated target comments/anchors
> something the texinfo exporter should handle?

There are no such things as "dedicated targets". Though
<> within a paragraph should be translated into some
sort of anchor. Isn't it the case?


Regards,

-- 
Nicolas Goaziou

Re: [O] Org interpreting multiple ^{*} instances as bold in LaTeX beamer export

[John Hendy]

On Wed, Feb 13, 2013 at 9:50 AM, Bastien  wrote:
> Hi John,
>
> John Hendy  writes:
>
>> I just wanted an asterisk to put a little footnote for two items in a
>> longer list and noticed that it shifted the whole slide up. Same for
>> regular LaTeX document export. Seems like it only happens if the two
>> bullets are consecutive.
>
> The last component of `org-emphasis-regexp-components' is the number
> of newlines allowed when emphasizing.  This is 1 by default, meaning
> that you cannot use markup on more than two consecutive lines.

Thanks for the explanation.

>
> In any case, you can simply use another character than "*" for the
> time being, we are working on this part of the code.  The plan is
> to allow to deactivate some markup based on a variable.
>

I just went with \star; close enough for me!


Thanks,
John

> Thanks,
>
> --
>  Bastien

Re: [O] [PATCH] Fix uncaught error when trying to open a link at point

[Bastien]

Hi Samuel,

Samuel Loury  writes:

> I am sorry for not sending the full patch myself: I am still waiting for
> the documents indicating I can contribute to emacs.

No problem at all.  I decided to go and accept patches from people
that did not confirm they got the FSF papers because merging 8.0
into Emacs trunk is not likely to happen to soon... So.  

-- 
 Bastien

[O] org-publish broken?

[henry atting]

Since the last git pull: org-mode version 7.9.3e (7.9.3e-1016-g2fa53e)
org-publish no longer works. Error message:

Publishing file file.org `org-publish-org-to-html'
org-publish-file: Symbol's function definition is void: org-publish-org-to-html

My (unchanged) settings:

 (setq org-publish-project-alist
   '(("org"
  :base-directory "~/horg/"
  :publishing-directory "~/public"
  :section-numbers nil
  :table-of-contents t
  :html-preamble nil
  :publishing-function org-publish-org-to-html
  :style "")
("org-static"
 :base-directory "~/horg/"
 :base-extension 
"css\\|js\\|png\\|jpg\\|gif\\|pdf\\|mp3\\|ogg\\|swf"
 :publishing-directory "~/public/"
 :recursive t
 :publishing-function org-publish-attachment
 )
))



-- 
henry, web: http://literaturlatenight.de
demnächst: http://literaturlatenight.de/blog/#sec-4
upcoming: http://literaturlatenight.de/blog/#sec-5

Re: [O] org-publish broken?

[Nicolas Goaziou]

Hello,

henry atting  writes:

> Since the last git pull: org-mode version 7.9.3e (7.9.3e-1016-g2fa53e)
> org-publish no longer works. Error message:
>
> Publishing file file.org `org-publish-org-to-html'
> org-publish-file: Symbol's function definition is void: 
> org-publish-org-to-html
>
> My (unchanged) settings:
>
>  (setq org-publish-project-alist
>'(("org"
>   :base-directory "~/horg/"
>   :publishing-directory "~/public"
>   :section-numbers nil
>   :table-of-contents t
>   :html-preamble nil
>   :publishing-function org-publish-org-to-html

The publishing function should be: `org-html-publish-to-html'

>   :style "  href=\"../.style.css\"
>  type=\"text/css\"/>")
>   ("org-static"
>:base-directory "~/horg/"
>  :base-extension 
> "css\\|js\\|png\\|jpg\\|gif\\|pdf\\|mp3\\|ogg\\|swf"
>  :publishing-directory "~/public/"
>  :recursive t
>  :publishing-function org-publish-attachment
>  )
> ))


Regards,

-- 
Nicolas Goaziou

Re: [O] org-publish broken?

[Bastien]

Hi Henry,

henry atting  writes:

> Since the last git pull: org-mode version 7.9.3e (7.9.3e-1016-g2fa53e)
> org-publish no longer works. Error message:
>
> Publishing file file.org `org-publish-org-to-html'
> org-publish-file: Symbol's function definition is void:
> org-publish-org-to-html

Since you are using Org from the master branch, 
you need to use org-html-publish-to-html from ox-html.el.

This is one of the incompatible changes that comes with
merging the new exporter.

Until 8.0 is released, I suggest publication should be
done from the maint branch.  Otherwise you'll need to
update your configuration.

HTH,

-- 
 Bastien

Re: [O] bbdb or bbdb3 or org-contacts

[Bastien]

Hi Grégoire,

Daimrod  writes:

> See the attached patch files. I still need to need to take into account
> what could be after the cursor

I've applied the patch against org-contacts.el, thanks for it.

Do you want write access to the repo for maintaining org-contacts.el?

> Moreover, `org-contacts.el' doesn't use the new parser from
> `org-element.el' ATM, and using it might improve the performance
> too.

Indeed!

-- 
 Bastien

Re: [O] Worg publishing issue

[Bastien]

Hi Suvayu,

Suvayu Ali  writes:

> In my file there are no begin_src blocks, however I do have
> begin_example blocks like the following:
>
>   #+begin_example
> ,#+LaTeX_CLASS: beamer
> ,#+LaTeX_CLASS_OPTIONS: [smaller,presentation]
> ,#+BEAMER_THEME: default
>   #+end_example
>
> I have not been following the list very closely for the last 5-6 months
> (too many deadlines in real life :(), has the above escaping syntax been
> changed?

The problem was not in your file at all, it was in a bug I introduced
in the maint branch, it is fixed now.  Worg is wide open to new contribs!

Thanks,

-- 
 Bastien

Re: [O] org-publish broken?

[henry atting]

Bastien  writes:

> Hi Henry,
>
> henry atting  writes:
>
>> Since the last git pull: org-mode version 7.9.3e (7.9.3e-1016-g2fa53e)
>> org-publish no longer works. Error message:
>>
>> Publishing file file.org `org-publish-org-to-html'
>> org-publish-file: Symbol's function definition is void:
>> org-publish-org-to-html
>
> Since you are using Org from the master branch, 
> you need to use org-html-publish-to-html from ox-html.el.
>
> This is one of the incompatible changes that comes with
> merging the new exporter.
>
> Until 8.0 is released, I suggest publication should be
> done from the maint branch.  Otherwise you'll need to
> update your configuration.

Since exporting now works but not at all properly I will stick to the
maint branch.


> HTH,

Thanks,

-- 
henry, web: http://literaturlatenight.de
demnaechst: http://literaturlatenight.de/blog/#sec-4
upcoming: http://literaturlatenight.de/blog/#sec-5

Re: [O] org-publish broken?

[Bastien]

henry atting  writes:

> Since exporting now works but not at all properly I will stick to the
> maint branch.

Well, exporting and publishing do work, but you need to adapt some
of your configuration for it to work.  We are in the process of
documenting this.  Any help is welcome!

Thanks,

-- 
 Bastien

Re: [O] link abbreviations and the /smb: method

[Bastien]

Hi Dieter,

"Dieter Wilhelm, H."  writes:

> for me the link abbreviation facility for local file names and http
> protocol addresses is working like a charm, but I don't get it to run
> with TRAMP's /smb method.  What are your experiences, is it not yet
> implemented?

My guess is that it depends on the version of Emacs/Tramp you are
using.  

Links of the form

#+LINK: myserver /ssh:u...@domain.org:/home/user/

works fine here.

-- 
 Bastien

[O] Offer for taking over maintainership

[Jambunathan K]

I offer to take over maintainership of Org.

Offer closes in 7 days.  Only pre-condition will be that Org-8.0 and
subsequent releases happen under my supervision.

Principals and riff-raffs can PM me with your thoughts.  I defend your
right to choose the maintainer or express yourself freely.

Note: Anger is futile, particularly over the internet.
-- 

Re: [O] bbdb or bbdb3 or org-contacts

[joakim]

Bastien  writes:

> Hi Grégoire,
>
> Daimrod  writes:
>
>> See the attached patch files. I still need to need to take into account
>> what could be after the cursor
>
> I've applied the patch against org-contacts.el, thanks for it.
>
> Do you want write access to the repo for maintaining org-contacts.el?
>
>> Moreover, `org-contacts.el' doesn't use the new parser from
>> `org-element.el' ATM, and using it might improve the performance
>> too.
>
> Indeed!

I've been using Daimrods patch for a while, and it makes org-contacts
entirely usable even for my 80kb contacts file. I'm looking forward to
further improvements!

-- 
Joakim Verona

Re: [O] Anchors in texinfo export

[Thomas S. Dye]

Nicolas Goaziou  writes:

> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Currently, the texinfo exporter translates a dedicated target in a comment:
>>
>> # <>
>
> This isn't a target. This is a comment that contains some text looking
> like Org syntax.
>

OK.  I see I have a note from you to revise the manual @ 4.2 Internal links:

  The preferred match for a text link is a dedicated target: the same
  string in double angular brackets. Targets may be located anywhere;
  sometimes it is convenient to put them into a comment line. For example

   # <>

>> to this:
>>
>> @c <>
>>
>> I was expecting to see a texinfo anchor:
>>
>> @anchor{x-export-to-odt}
>>
>> There are a handful of these dedicated target comments cum anchors in the Org
>> mode manual. I believe all of them are in places where it would be easy
>> to replace them with links directly to the corresponding headline/node.
>>
>> Should I edit them away? Or, are dedicated target comments/anchors
>> something the texinfo exporter should handle?
>
> There are no such things as "dedicated targets". Though
> <> within a paragraph should be translated into some
> sort of anchor. Isn't it the case?

I don't know yet.  AFAICT there isn't a need for this construct in the
Org mode manual.

At any rate, I'll go ahead and get rid of the comments that contain this
text with apparent Org mode syntax and replace the links to them with
links back to the corresponding headlines.

All the best,
Tom

-- 
T.S. Dye & Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com

Re: [O] Anchors in texinfo export

[Nicolas Goaziou]

t...@tsdye.com (Thomas S. Dye) writes:

> Nicolas Goaziou  writes:
>
>> Hello,
>>
>> t...@tsdye.com (Thomas S. Dye) writes:
>>
>>> Currently, the texinfo exporter translates a dedicated target in a comment:
>>>
>>> # <>
>>
>> This isn't a target. This is a comment that contains some text looking
>> like Org syntax.
>>
>
> OK.  I see I have a note from you to revise the manual @ 4.2 Internal links:
>
>   The preferred match for a text link is a dedicated target: the same
>   string in double angular brackets. Targets may be located anywhere;
>   sometimes it is convenient to put them into a comment line. For example
>
># <>
>
>>> to this:
>>>
>>> @c <>
>>>
>>> I was expecting to see a texinfo anchor:
>>>
>>> @anchor{x-export-to-odt}
>>>
>>> There are a handful of these dedicated target comments cum anchors in the 
>>> Org
>>> mode manual. I believe all of them are in places where it would be easy
>>> to replace them with links directly to the corresponding headline/node.
>>>
>>> Should I edit them away? Or, are dedicated target comments/anchors
>>> something the texinfo exporter should handle?
>>
>> There are no such things as "dedicated targets". Though
>> <> within a paragraph should be translated into some
>> sort of anchor. Isn't it the case?
>
> I don't know yet.  AFAICT there isn't a need for this construct in the
> Org mode manual.
>
> At any rate, I'll go ahead and get rid of the comments that contain this
> text with apparent Org mode syntax and replace the links to them with
> links back to the corresponding headlines.

For completeness, when you put a target <> somewhere, optimally
(this obviously depends on the back-end):

  - [[target]] should link to it and be displayed as the ordinal of the
environment containing it (a.k.a cross-reference).

  - [[target][text]] should link to it and be displayed as "text".

Also, there is a special #+TARGET: keyword. It will never be exported
and links to it will be ignored. It allows for quick navigation in an
Org buffer without impacting export.


Regards,

-- 
Nicolas Goaziou

Re: [O] [Warnings] HTML produced by new exporter

[Nicolas Goaziou]

Hello,

"Sebastien Vauban"
 writes:

> I exported a simple file:
>
> #+TITLE: Example of Tasks
> #+AUTHOR:Sebastien Vauban
> #+Time-stamp: <2013-02-12 Tue 16:04>
> #+DESCRIPTION:
> #+KEYWORDS:
> #+LANGUAGE:  en
>
> * Marketing
>
> ** STRT Hire PR firm   :phone:
>
> and ran `tidy' on it.
>
> It reported 2 warnings:
>
> 63:59: Warning: nested emphasis 
> 81:126: Warning: nested emphasis 
>
> They come from the tag, once in the TOC, once in the headline:
>
> 1.1. Hire PR firm    class="tag">phone
> ...
> 1.1 STRT Hire PR firm    class="phone">phone

I am no HTML specialist. It is wrong? What do you suggest instead?


Regards,

-- 
Nicolas Goaziou

Re: [O] SETUPFILE and variants

[Nicolas Goaziou]

Hello,

"Sebastien Vauban"
 writes:

> With the new exporter, I still couldn't find how to use a setup file.
>
> Neither with:
>
> - the old `#+SETUPFILE:' directive

Still working here.

> - the new one (?): `#+SETUP_FILE:'

It has been dropped. You can safely forget it.

> - the soon to be unique one (?): `#+INCLUDE:'

It should work too.

I had indeed considered dropping #+SETUPFILE. but if we keep it, we
might be able to define an :EXPORT_SETUPFILE: for subtree export (not
implemented). So, after all, I

Anyway, for the time being, I prefer to focus on real bugs.

> ECM file:
>
> #+TITLE: Example of Tasks
> #+AUTHOR:Sebastien Vauban
> #+DESCRIPTION:
> #+KEYWORDS:
> #+LANGUAGE:  en
>
> #+INCLUDE: "~/src/org-style/bigblow.setup"
>
> * Marketing
>
> ** STRT Hire PR firm

What does "bigblow.setup" contain? I have no problem with this ECM.

Also what did you expect?


Regards,

-- 
Nicolas Goaziou

Re: [O] Offer for taking over maintainership

[Jambunathan K]

Jambunathan K  writes:

> I offer to take over maintainership of Org.
>
> Offer closes in 7 days.  

Adding a note to myself.  Feb 20, IST

> Only pre-condition will be that Org-8.0 and subsequent releases happen
> under my supervision.
>
> Principals and riff-raffs can PM me with your thoughts.  I defend your
> right to choose the maintainer or express yourself freely.
>
> Note: Anger is futile, particularly over the internet.

-- 

[O] segfault on 'make test'

[Gregory Benjamin]

I did a 'git pull' just now, followed by 'make test' and this is what
happened (snippet shown for brevity):


Code block evaluation complete.
   passed  281/342  test-org-property-accumulation-top-use
OVERVIEW
executing Emacs-Lisp code block...

(foo (quote 1))

(bar (quote 2))

Code block evaluation complete.
   passed  282/342  test-org-property-accumulation-top-val
OVERVIEW
Mark set
Fatal error (11)Segmentation fault
make: *** [test] Error 139


So it looks like test number 283 blew up.
I'm happy to try investigating with some help...

The basic system info:

  $ uname -a
  Linux dbn66 2.6.32-5-amd64 #1 SMP Sun Sep 23 10:07:46 UTC 2012 x86_64 
GNU/Linux

  $ lsb_release -sd
  Debian GNU/Linux 6.0.6 (squeeze)

Best,
Greg Benjamin

Re: [O] [Warnings] HTML produced by new exporter

[Sebastien Vauban]

Hi Nicolas,

Nicolas Goaziou wrote:
> "Sebastien Vauban" writes:
>
>> I exported a simple file:
>>
>> * Marketing
>>
>> ** STRT Hire PR firm   
>> :phone:
>>
>> and ran `tidy' on it.
>>
>> It reported 2 warnings:
>>
>> 63:59: Warning: nested emphasis 
>> 81:126: Warning: nested emphasis 
>>
>> They come from the tag, once in the TOC, once in the headline:
>>
>> 1.1. Hire PR firm   > class="tag">phone
>> ...
>> 1.1 STRT Hire PR firm   > class="phone">phone
>
> I am no HTML specialist.

So am I (not).

> It is wrong? What do you suggest instead?

Trying to find information about how to solve this, I came across this post
(in French):

Lorsque HTML Tidy te dit ça, ce n'est qu'une recommandation. C'est valide 
syntaxiquement parlant.

  ╭ Modified from 
http://forum.alsacreations.com/topic-2-2793-1-resoluBalises-span-imbriquees.html
  │
  │ HTML Tidy ne sait pas que c'est pour la présentation, et lui voit 
simplement :
  │
  │ Truc
  │
  │ Donc en fait, ton code ne comporte aucune erreur
  ╰

The conclusion is: just a comment, no real error. Closed!

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] Problem to export an orgmode file to pdf

[Sebastien Vauban]

Hi Steve,

"Steve Prud'Homme" wrote:
> ! LaTeX Error: Missing \begin{document}.

Out of curiosity, is there a \documentclass macro at the top of the exported
TeX file?

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] Worg publishing issue

[Suvayu Ali]

On Wed, Feb 13, 2013 at 06:32:46PM +0100, Bastien wrote:
> 
> The problem was not in your file at all, it was in a bug I introduced
> in the maint branch, it is fixed now.  Worg is wide open to new contribs!

Thanks a lot Bastien!

-- 
Suvayu

Open source is the future. It sets us free.

[O] Option H: and texinfo export

[Thomas S. Dye]

Aloha all,

When the H: option is set to a number > 4, the texinfo exporter
generates a detailed node listing with links to nodes that texinfo
doesn't recognize.  IIUC, texinfo recognizes nodes for chapter, section,
subsection, and subsubsection, but not for any lower level divisions of
the document.

Is there a context where H:5..n would make sense in a document exported
to texinfo?  If not, should the exporter behave differently in this
instance?

These are just questions, not requests for changes to the code.  I have
H:4 and things seem to be working beautifully :)
 
All the best,
Tom

-- 
T.S. Dye & Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com

Re: [O] new HTML export backend: footnote format [%s]?

[Stefan Vollmar]

Dear Nick,

On 13.02.2013, at 02:58, Nick Dokos wrote:

> Stefan Vollmar  wrote:
> 
>> I have just started using the new exporter in 7.9.3e (7.9.3e-999-ge5322) for 
>> HTML output.
>> 
>> [...] This apparently does not have an effect any more:
>> (setq org-export-html-footnote-format " [%s]")
>> - is there a new way to configure this format for the new export backends 
>> (we prefer "[123]" references to superscripted footnotes)?
>> 
> 
> Probably (i.e. I did not test),  customizing these two:
> 
> ,
> | (defcustom org-html-footnote-format "%s"
> |   "The format for the footnote reference.
> | %s will be replaced by the footnote reference itself."
> |   :group 'org-export-html
> |   :type 'string)

indeed:
(setq org-html-footnote-format " [%s]")
does the trick.

Thanks!
Warm regards,
 Stefan
-- 
Dr. Stefan Vollmar, Dipl.-Phys.
Head of IT group
Max-Planck-Institut für neurologische Forschung
Gleuelerstr. 50, 50931 Köln, Germany
Tel.: +49-221-4726-213  FAX +49-221-4726-298
Tel.: +49-221-478-5713  Mobile: 0160-93874279
Email: voll...@nf.mpg.de   http://www.nf.mpg.de








smime.p7s
Description: S/MIME cryptographic signature

Re: [O] orgstruct-mode with custom headline prefix

[Achim Gratz]

Christopher Schmidt writes:
> I did that now.
>
> d6f69f5 org.el: Use let instead of progv in org-run-like-in-org-mode
> ea2d107 org.el: Declare orgstruct-mode

Thanks for fixing this.


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

SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

Re: [O] segfault on 'make test'

[Bastien]

Hi Gregory,

Gregory Benjamin  writes:

> Code block evaluation complete.
>passed  282/342  test-org-property-accumulation-top-val
> OVERVIEW
> Mark set
> Fatal error (11)Segmentation fault
> make: *** [test] Error 139

What version of Emacs are you using?  I assume you are on the current
HEAD of the master branch, but M-x org-version RET can help too.

Thanks!

-- 
 Bastien

Re: [O] segfault on 'make test'

[Achim Gratz]

Gregory Benjamin writes:
> I did a 'git pull' just now, followed by 'make test'

Nothing to do with your problem, but "ake up1" would do this with less
typing.  :-)


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

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada

Re: [O] SETUPFILE and variants

[Sebastien Vauban]

Nicolas, Bastien,

"Sebastien Vauban" wrote:
>>> ECM file:
>>>
>>> #+TITLE: Example of Tasks
>>> #+AUTHOR:Sebastien Vauban
>>> #+DESCRIPTION:
>>> #+KEYWORDS:
>>> #+LANGUAGE:  en
>>>
>>> #+INCLUDE: "~/src/org-style/bigblow.setup"
>>>
>>> * Marketing
>>>
>>> ** STRT Hire PR firm
>>
>> What does "bigblow.setup" contain?
>
> In essence: links to CSS and JavaScript "libraries"

By the way, it'd be wonderful if we could put an URL to the setup file: that
way, for documents we edit together, I don't have either:

- to impose an absolute location for the setup file, nor
- to copy the setup file locally in every project we collaborate on.

Is that somehow doable?

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] Offer for taking over maintainership

[John Wiegley]

> Jambunathan K  writes:

> I offer to take over maintainership of Org.
> Offer closes in 7 days.  Only pre-condition will be that Org-8.0 and
> subsequent releases happen under my supervision.
> 
> Principals and riff-raffs can PM me with your thoughts.  I defend your right
> to choose the maintainer or express yourself freely.

I don't know, Jambunathan, the tone of this offer makes me inclined to reject
it.  I didn't even realize Bastien was looking for a replacement.

John

Re: [O] Offer for taking over maintainership

[Allen S. Rout]

On 02/13/2013 03:45 PM, John Wiegley wrote:

>  I didn't even realize Bastien was looking for a replacement.


There's no technical reason someone interested in making an offer should
necessarily wait for a declared vacancy.  It seems a straightforward
move of no-confidence, soliciting support.



It would probably be most peaceful not to discuss Jambunathan's offer on
this forum.   I expect that the count of +1s to the offer will
communicate the list's collective opinion.


- Allen S. Rout

Re: [O] Offer for taking over maintainership

[Russell Adams]

> It would probably be most peaceful not to discuss Jambunathan's offer on
> this forum.   I expect that the count of +1s to the offer will
> communicate the list's collective opinion.

I've ignored Jambunathan so far, hoping that not feeding the troll
will make it go away. I understand he's contributed significant code,
but his combative attitude is an instant turn off. I can't imagine a
team leader (which is what I consider a maintainer) having such a
negative attitude. Often team leads require better people skills than
coding skills because most of their time is spent in team management,
I see no evidence of superior skills being demonstrated here.

I'll also point out that I can always tell when Bastien comes back
from an announced vacation, suddenly my inbox fills up with replies to
everything that hasn't been answered yet. I'm impressed with Bastien's
staying power and people skills, he needs no replacement.

-1

--
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] Offer for taking over maintainership

[Charles Philip Chan]

Jambunathan K  writes:

> I offer to take over maintainership of Org.
>
> Offer closes in 7 days.  Only pre-condition will be that Org-8.0 and
> subsequent releases happen under my supervision.
>
> Principals and riff-raffs can PM me with your thoughts.  I defend your
> right to choose the maintainer or express yourself freely.
>
> Note: Anger is futile, particularly over the internet.

I refrained from posting until this coup. Jambunathan, I appreciate your
contributions to org-mode. However, your attitude just pisses me
off. Being a good maintainer needs people skills which you obviously
lack. My vote is "-1".

Charles

-- 
"People get annoyed when you try to debug them."

  -- Larry Wall (Open Sources, 1999 O'Reilly and Associates)


pgpmWmRk3t6UM.pgp
Description: PGP signature

Re: [O] Offer for taking over maintainership

[Yagnesh Raghava Yakkala]

Dear Jambunathan,

On Feb 14 2013, Jambunathan K  wrote:

> express yourself freely.

By taking advantage of that opportunity, expressing my voice here. Feel *free
to ignore/dismiss* it.

As a competent programmer and strong FSF supporter you can play a bigger role
in the broader field(i.e., Emacs). Since you have now got commit access to
Emacs core, you can contribute more to the Emacs as a whole while maintaining
org-odt from Emacs. I see you have some interest in CEDET as well, or maybe
you could also bless us with some other great project just like Org.

That said, Org community(including you) will remember your kind offer and asks
your help when it is necessary.

Thanks.,
-- 
ఎందరో మహానుభావులు అందరికి వందనములు.
YYR

Re: [O] bbdb or bbdb3 or org-contacts

[Daimrod]

Bastien  writes:

> Hi Grégoire,
>
> Daimrod  writes:
>
>> See the attached patch files. I still need to need to take into account
>> what could be after the cursor
>
> I've applied the patch against org-contacts.el, thanks for it.

Thank you.

> Do you want write access to the repo for maintaining org-contacts.el?

I would love to. I've made some changes to `org-contacts.el' and Joakim
has been very kind to test them, but there is still a lot of room for
improvements (and bugs).

However, I think I'll keep my public repository on github to test new
features and merge them into upstream when I think they're ready. And if
people can test them before that, it's even better.

>> Moreover, `org-contacts.el' doesn't use the new parser from
>> `org-element.el' ATM, and using it might improve the performance
>> too.
>
> Indeed!

-- 
Daimrod/Greg


pgpWOIookBxzg.pgp
Description: PGP signature

Re: [O] Offer for taking over maintainership

[Bastien]

Dear all,

Jambunathan (like anyone) is free to fork the code, to build
a community around his fork and to submit his changes to Emacs.
He has commit access to Emacs, so that should even make things
easier for him.

This is free software, and the ability to fork is what makes
sure we are all focused on software, not on personal issues.

I am not actively looking for a new maintainer right now, I'm 
focusing on releasing Org 8.0 -- like all other contributors.

I've been long thinking of stepping down, but I don't want to
make this move before I have found someone me and longstanding
contributors feel comfortable interacting with.

Stay tuned!

Thanks,

-- 
 Bastien

Re: [O] bbdb or bbdb3 or org-contacts

[Bastien]

Hi Greg,

Daimrod  writes:

> However, I think I'll keep my public repository on github to test new
> features and merge them into upstream when I think they're ready. And if
> people can test them before that, it's even better.

no problem, don't hesitate to share the patches.

Thanks!

-- 
 Bastien

Re: [O] bbdb or bbdb3 or org-contacts

[Daimrod]

Bastien  writes:

> Hi Greg,
>
> Daimrod  writes:
>
>> However, I think I'll keep my public repository on github to test new
>> features and merge them into upstream when I think they're ready. And if
>> people can test them before that, it's even better.
>
> no problem, don't hesitate to share the patches.
>
> Thanks!

I think I haven't been clear, I would like to have write access to the
upstream repository to merge my changes, but I will also keep my github
version as a "bleeding edge" version to make it easier to test and
propose changes without pushing into the upstream repository.

-- 
Daimrod/Greg


pgpR2VqFi3Djt.pgp
Description: PGP signature

Re: [O] Offer for taking over maintainership

[François Pinard]

Jambunathan K  writes:

> I offer to take over maintainership of Org.

-1

François

P.S. I love the Org project, and I strongly hope it stay lovable.  The
human qualities of a maintainer, and the crowd surrounding him/her, are
very important to me.  In the past, I left projects, languages and even
duties just to make sure I stay surrounded by nice people.  And I
succeeded so far, and met many extraordinary people that changed my
life.  I would be sad if I had to get away from a very satisfying
project, merely because it stops being a warm place to be.

Re: [O] Offer for taking over maintainership

[Takaaki ISHIKAWA]

Dear all,

I cannot see any reason to change the maintainer.
My vote is "-1".

Best regards,
Takaaki Ishikawa



--
Takaaki ISHIKAWA 
  GITI, Waseda University
( ' -')b http://about.me/takaxp


On 2013年2月14日Thursday at 3:08, Jambunathan K wrote:

>  
> I offer to take over maintainership of Org.
>  
> Offer closes in 7 days. Only pre-condition will be that Org-8.0 and
> subsequent releases happen under my supervision.
>  
> Principals and riff-raffs can PM me with your thoughts. I defend your
> right to choose the maintainer or express yourself freely.
>  
> Note: Anger is futile, particularly over the internet.
> --  

Re: [O] Offer for taking over maintainership

[Jonathan Leech-Pepin]

On 13 February 2013 13:08, Jambunathan K  wrote:

>
> I offer to take over maintainership of Org.
>

I have to say -1 as well.

>
> Offer closes in 7 days.  Only pre-condition will be that Org-8.0 and
> subsequent releases happen under my supervision.
>
Is there something in particular about the forthcoming 8.0 that you would
want done differently from how it currently is being done?  Considering
Bastien's
current plan is to push towards releasing it in the near future.


>
> Principals and riff-raffs can PM me with your thoughts.  I defend your
>  right to choose the maintainer or express yourself freely.
>

The tone in this bit, classifying readers of the list either as principals
(I'm assuming
this would be Bastien and others who are highly active in maintaining and
updating
Org) or riff-raff (meaning the rest of the user base?) is hardly endearing.

I appreciate the org-odt exporter, I haven't had much use for it but what I
have had to
use it for it worked perfectly.  However your attitude in the past has
often struck me as
abrasive or argumentative when there was little to no reason for it.
 Either there's some
underlying reason for your apparent dislike for Bastien and his approach to
maintaining
Org, or some argument in the past that I am not aware of.

Regardless, Bastien is doing a fine job from what I can see, he is
certainly actively assisting
users who post with questions or bugs, even when they occurred during a
time where he was
absent (with prior notice).  Perhaps he has not contributed to certain
aspects as others have,
however his presence and monitoring of the smaller aspects does allow for
further development
to proceed without being interrupted by every issue.

Regards,
Jon
--

Note: Anger is futile, particularly over the internet.
> --
>
>

Re: [O] Problem to export an orgmode file to pdf

[Steve Prud'Homme]

24.2.1 (i686-pc-cygwin)


2013/2/13 Bastien 

> Hi Steve,
>
> "Steve Prud'Homme"  writes:
>
> > I have a problem. When i try to export my orgmode file de pdf c-c c-e p
> > i have this message and no pdf file, what can i do to resolve the
> > problem.
>
> What version of Emacs/Org are you using?
>
> --
>  Bastien
>



-- 
Posté par Steve Prud'Homme
sprud...@gmail.com
514 466-3951

Re: [O] org-end-of-line deactivating region?

[Eric Abrahamsen]

Bastien  writes:

> Hi Eric,
>
> Eric Abrahamsen  writes:
>
>> Has anyone noticed this? With emacs -Q, the latest Org, and
>> org-special-ctrl-a/e set to t, activating the region and then hitting
>> C-e org-end-of-line deactivates the region. Am I dreaming?
>
> I can't reproduce this.  ECM?

Neither can I, now... Dunno what happened. Sorry for the noise.

Re: [O] Offer for taking over maintainership

[Scott Randby]

On 02/13/2013 04:41 PM, Russell Adams wrote:
>> It would probably be most peaceful not to discuss Jambunathan's offer on
>> this forum.   I expect that the count of +1s to the offer will
>> communicate the list's collective opinion.
> 
> I've ignored Jambunathan so far, hoping that not feeding the troll
> will make it go away. I understand he's contributed significant code,
> but his combative attitude is an instant turn off. I can't imagine a
> team leader (which is what I consider a maintainer) having such a
> negative attitude. Often team leads require better people skills than
> coding skills because most of their time is spent in team management,
> I see no evidence of superior skills being demonstrated here.
> 
> I'll also point out that I can always tell when Bastien comes back
> from an announced vacation, suddenly my inbox fills up with replies to
> everything that hasn't been answered yet. I'm impressed with Bastien's
> staying power and people skills, he needs no replacement.
> 

I'm in 100% agreement with this excellent statement.

Scott Randby

[O] using export filters to emulate multi-column table cells?

[Eric Abrahamsen]

Is there any way to use the new exporter mechanisms to emulate table
cells that span rows or columns on export? I'm envisioning something
like this:

|  | <2col>Grains  |   |
| Year | Oats  | Wheat |
| 2007 | 10lbs | 40lbs |

Where an export filter would pick up on the <2col> cookie, replace it
with something backend-specific like \multicolumn{2}{Grains}, and then
somehow remove the following table field from export.

No clue how feasible that might be...

Eric

Re: [O] Offer for taking over maintainership

[Jambunathan K]

You seem to stand out in the mob.  So some personal hugs from side.

>> Offer closes in 7 days.  Only pre-condition will be that Org-8.0 and
>> subsequent releases happen under my supervision.
>>
> Is there something in particular about the forthcoming 8.0 that you
> would want done differently from how it currently is being done?
> Considering Bastien's current plan is to push towards releasing it in
> the near future.

I wish more people ask an open-ended question rather than sit in
judgement seat.  Trial by jury is always interesting.  (There is also an
interesting movie I have seen on this topic, decades ago.)

> I appreciate the org-odt exporter, I haven't had much use for it but
> what I have had to use it for it worked perfectly.  However your
> attitude in the past has often struck me as abrasive or argumentative
> when there was little to no reason for it.  Either there's some
> underlying reason for your apparent dislike for Bastien and his
> approach to maintaining Org, or some argument in the past that I am
> not aware of.

Why would most people think that I am a moron.  The last line is
exemplary of what the jury and the judge should mull about.

ps-1: I refuse to answer your questions.  The debate and offer is on my
  terms if people don't understand it.

ps-2: I am calling everyone's bluff, if you haven't realized it already.
  (Believe me, I am not acting like a smart donkey here.)

ps-3: An extra and a proven hand helps particularly in volunteer driven
  efforts.  My palm could be stinking?  Does that mean my code
  stinks.  Most people would rather talk, than look, think, ask or
  do?
-- 

Re: [O] Offer for taking over maintainership

[Jambunathan K]

(Discussion is meta.  So bear with my amateurish excursions.)

Some times the best question to ask is NOT "What I stand to gain?" but
"What I/We stand to lose?".  Are the overheads worth it in the long run?

Everyone wants to gain all the time without losing anything.  I call
that interesting.

Jambunathan K  writes:

> You seem to stand out in the mob.  So some personal hugs from side.
>
>>> Offer closes in 7 days.  Only pre-condition will be that Org-8.0 and
>>> subsequent releases happen under my supervision.
>>>
>> Is there something in particular about the forthcoming 8.0 that you
>> would want done differently from how it currently is being done?
>> Considering Bastien's current plan is to push towards releasing it in
>> the near future.
>
> I wish more people ask an open-ended question rather than sit in
> judgement seat.  Trial by jury is always interesting.  (There is also an
> interesting movie I have seen on this topic, decades ago.)
>
>> I appreciate the org-odt exporter, I haven't had much use for it but
>> what I have had to use it for it worked perfectly.  However your
>> attitude in the past has often struck me as abrasive or argumentative
>> when there was little to no reason for it.  Either there's some
>> underlying reason for your apparent dislike for Bastien and his
>> approach to maintaining Org, or some argument in the past that I am
>> not aware of.
>
> Why would most people think that I am a moron.  The last line is
> exemplary of what the jury and the judge should mull about.
>
> ps-1: I refuse to answer your questions.  The debate and offer is on my
>   terms if people don't understand it.
>
> ps-2: I am calling everyone's bluff, if you haven't realized it already.
>   (Believe me, I am not acting like a smart donkey here.)
>
> ps-3: An extra and a proven hand helps particularly in volunteer driven
>   efforts.  My palm could be stinking?  Does that mean my code
>   stinks.  Most people would rather talk, than look, think, ask or
>   do?

-- 

Re: [O] ocaml babel no longer works?

[Alan Schmitt]

Hi Eric,

Eric Schulte writes:

>> The suggestion: instead of appending '"org-babel-ocaml-eoe";;' to the
>> code, how simply put ';;' (which will make sure everything is flushed)
>> then detect the toplevel is done by seeing the string '# ' at the
>> beginning of the line? Would there be an issue with the fact that this
>> line does not have a newline? If so, an alternative suggestion would be
>> to use the longer ';; "org-babel-ocaml-eoe";;' which makes sure the
>> phrase in the input won't interact with the marker.
>>
>
> You can customize the `org-babel-ocaml-eoe-output' and
> `org-babel-ocaml-eoe-indicator' variables so that they match the above.
> If this proves generally useful then I'd be happy to admit this change
> to the core.

I'll have a look at it (as soon as my European grant deadline as
passed). The one thing I don't know about org-babel-comint-with-output
is the following: what does it do with the last line if it does not have
a carriage return? (After running a command, the toplevel outputs '# '
with no carriage return. Will it be part of the returned string?)

> I hope these pointers are useful.

They definitely are. As ocaml is not only my language of choice but one
I have the chance of teaching, I'll clearly look into this.

Thanks again,

Alan

Re: [O] bbdb or bbdb3 or org-contacts

[Gour]

Daimrod  writes:

> I would love to. I've made some changes to `org-contacts.el' and Joakim
> has been very kind to test them, but there is still a lot of room for
> improvements (and bugs).

Thank you for taking care about org-contacts which makes me inspired to
try using it for my Emacs-based contact manager. I don't like idea to
keep contacts @Google and bbdb3 might not be as flexible as
org-contacts.


Sincerely,
Gour

-- 
It is far better to discharge one's prescribed duties, even though 
faultily, than another's duties perfectly. Destruction in the course 
of performing one's own duty is better than engaging in another's duties, 
for to follow another's path is dangerous.


pgpd986lFQ7b1.pgp
Description: PGP signature

Re: [O] Offer for taking over maintainership

[David Rogers]

Jambunathan K  writes:

> I offer to take over maintainership of Org.

Org right now is making quick progress, important improvements, and has
a lot of enthusiastic and useful contributors. When a maintainer
decision needs to be made, there is usually a satisfactory result. (Not
to say there are no arguments - but every software project has
arguments.)  Questions get answered properly, people are able and
willing to help each other, number of users seems to be large. It is
hard to imagine that a campaign to change the leadership style would do
anything good, and easy to imagine that it could be destructive.

-1

-- 
David