Re: [O] sticky agenda and clock persistence interaction

[Bastien]

Achim Gratz strom...@nexgo.de writes:

 Brian van den Broek writes:
 (setq org-agenda-sticky t)

 That's a defcustom and you should not try to setq it unless you really
 know when and how defcustom does its thing (I don't).

What's wrong with setq'ing a variable defined with defcustom?

AFAIK that's the usual way to add customization in your init file,
independantly of the customization you add through the customize
interface.  And that's the way advertized in the Emacs manual too.

-- 
 Bastien

Re: [O] [OT] Current website not very attractive

[Bastien]

Yes, there is a problem here: only users with push access can 
clone for now (and pull and push.)

I think Jason is not online this week-end, so we will have to
live with it.

I've created clones of org-mode.git and orgweb.git on github:

  https://github.com/bzg/org-mode
  https://github.com/bzg/orgweb

HTH,

-- 
 Bastien

Re: [O] Org-mode version N/A-fixup

[Bastien]

Hi Markus,

Markus Heller helle...@gmail.com writes:

 Anyhow, git *is* in my PATH, but I think my issue is that I don't know
 how to update a git repo from *within* emacs.

 Would you be able to give pointers please?

M-x eshell RET
~$ cd install/git/org-mode
~$ git pull

... 

But I think I lost track of the initial problem, so maybe we are
miscommunicating here.  As long as your install is okay, I'll be
okay.

-- 
 Bastien

Re: [O] Invalid function: with-parsed-tramp-file-name with Perl

[Bastien]

Hi Achim,

Achim Gratz strom...@nexgo.de writes:

 It doesn't automatically propagate.  Otherwise, it's Bastiens decision —
 I can push the change if he wants to.

Can you summarize what would be the change and why it is called for?

Thanks,

-- 
 Bastien

Re: [O] Invalid function: with-parsed-tramp-file-name with Perl

[Achim Gratz]

Bastien writes:
 Can you summarize what would be the change and why it is called for?

The tag release_7.8.11 is affixed to the merge commit, which means that
it's first parent is on the master branch rather than maint.  The change
sets it back one commit so that it correctly is located on the maint
branch.

We'll have to tell users to forcibly update the tags again.


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

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves

Re: [O] An org-attach link type [7.9.1 (7.9.1-elpa @ /home/youngfrog/.emacs.d/elpa/org-20120903/)]

[Viktor Rosenfeld]

Hi Nicolas,

I played around with your function and it's pretty nifty, but I had to make
a few changes to get it working:

- I have to load the cl module, otherwise the case function is void.
- I had to replace find-lisp-find-files with directory-files because
  the former does not exist on my Emacs installation. I use GNU Emacs
  24.2.1 on OS X compiled from MacPorts.
- I don't need to map the returned files to their relative paths.
- I couldn't find a difference between the 'relative and 'full options.
  org-attach-expand-link always returns the path as specified in the
  ATTACH_DIR property or constructed from the ID, but never the full
  (absolute) path unless it is explicitly specified. In other words, it
  does the same thing as your code for the 'relative options. I've
  removed both options and replaced it with a 'file option that calls
  org-attach-expand-link.
- I use attach instead of att as a link prefix in my files and had
  to change the names of the functions. Sorry about that, but I did not
  want to fix all my links.

Code is below. I'm using Org-mode 7.9.1.

Cheers,
Viktor

#+BEGIN_SRC emacs-lisp
(defvar org-attach-complete-how 'attach
  Determines how org-attach-complete-link completes links to attachments.

It can be the symbols :
- `file' :: A \file:\ link is returned including the attachment directory.
- `attach' :: An \attach:\ link is returned.)

(require 'cl)

(defun org-attach-complete-link ()
  File completion for the \attach\ filetype in `org-mode'.
  (let* ((attach-dir (org-attach-dir nil))
 files file)
(unless attach-dir
  (error No attachment dir.))
(setq files (directory-files attach-dir nil ^[^.].*[^~]$ nil)
  file (org-icompleting-read Find attachment:  files))
(case org-attach-complete-how
  ('file (org-attach-expand-link file))
  ('attach (concat attach: file)
#+END_SRC

Nicolas Richard wrote:

 Hello there,
 
 Some people already have suggested and produced some code (see [1,2]) in
 order to have an attach (or att, as it was called) link type in
 org-mode. I never found a org--complete-link function for these links
 on the net, so I tried to write it for myself. In order to do that, I had
 to modify org-insert-link so that the org-mode buffer is made current
 (instead of *Org Links*) when calling org-link-try-special-completion.
 This allows the org--complete-link family of functions to access the actual
 org buffer from which org-insert-link was called. A patch in this direction
 is at the end of my email. (This is the first time that I use
 git-format-patch, I hope I got that right).
 
 With that change, here is some code that adds an att link type with 
 completion:
 
 (defun org-att-complete-link ()
   File completion for the \att\ filetype in `org-mode'.
   (let* ((attach-dir (org-attach-dir nil))
  files file)
 (unless attach-dir
   (error No attachment dir.))
 (setq files (find-lisp-find-files attach-dir ^[^.].*[^~]$)
   file (org-icompleting-read Find attachment: 
(mapcar 
 (lambda (x) (file-relative-name x 
 attach-dir))
 files)
nil t))
 (case org-att-complete-how
   ('full (org-attach-expand-link file))
   ('relative (concat file: attach-dir file))
   ('attach (concat att: file)
 (defvar org-att-complete-how 'attach
 Determines how org-att-complete-link completes links to attachments.
 
 It can be the symbols :
 - `full' :: A \file:\ link with full path is returned,
 - `relative' :: a \file:\ link containg a path relative to the directory 
 where the org-file resides is returned, or
 - `attach' :: an \att:\ link is returned.
 
 `full' is probably best avoided.)
 
 (org-add-link-type att 'org-att-open-link)
 (defun org-att-open-link (file)
   (org-open-file (org-attach-expand file)))
 
 I hope that this is useful to anybody, and not too sloppy (I'm not
 fluent in elisp)
 
 [1] http://lists.gnu.org/archive/html/emacs-orgmode/2011-04/msg00010.html
 [2] http://lists.gnu.org/archive/html/emacs-orgmode/2011-02/msg00952.html
 
 
 The patch for the above mentionned change in org.el follows :
 
 -- 8 --
 Subject: [PATCH] Allow org--complete-read family of functions to access
  current-buffer
 
 This allows for link-completion features based on information around the 
 point.
 ---
  lisp/org.el | 3 ++-
  1 file changed, 2 insertions(+), 1 deletion(-)
 
 diff --git a/lisp/org.el b/lisp/org.el
 index 3dfd073..fc5d709 100644
 --- a/lisp/org.el
 +++ b/lisp/org.el
 @@ -9411,6 +9411,7 @@ If the DEFAULT-DESCRIPTION parameter is non-nil, this 
 value will
  be used as the default description.
(interactive P)
(let* ((wcf (current-window-configuration))
 +  (buffer (current-buffer))
(region (if (org-region-active-p)
(buffer-substring (region-beginning) (region-end
(remove (and 

Re: [O] [OT] Current website not very attractive

[Nick Dokos]

Bastien b...@altern.org wrote:

 Yes, there is a problem here: only users with push access can 
 clone for now (and pull and push.)
 
 I think Jason is not online this week-end, so we will have to
 live with it.
 
 I've created clones of org-mode.git and orgweb.git on github:
 
   https://github.com/bzg/org-mode
   https://github.com/bzg/orgweb
 

Just tell people to use http: instead of git: for now.

Nick

Re: [O] org-wikinodes - is there a limit of processable files/nodes

[Bastien]

Hi Marcelo,

Marcelo de Moraes Serpa celose...@gmail.com writes:

 Why? Because I have files in other directory levels that I still want
 to link to the wiki, so basically I want to force all wikilinks to
 point to nodes in org files that reside in this wiki/ directory only.

I just pushed some changes in org-wikinodes.el, maybe they will solve
your problem.  Let me know.

Thanks,

-- 
 Bastien

Re: [O] [OT] Current website not very attractive

[Bastien]

Nick Dokos nicholas.do...@hp.com writes:

 Just tell people to use http: instead of git: for now.

All right, you just did so.  Thanks,

-- 
 Bastien

Re: [O] LaTeX export problem

[Nicolas Goaziou]

Hello,

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

 (require 'org-special-blocks)

You can remove this line. `org-special-blocks' is obsolete with the new
exporter.


Regards,

-- 
Nicolas Goaziou

Re: [O] org-e-groff-export-to-groff produces empty output file

[Nicolas Goaziou]

Hello,

Luis Anaya papoan...@hotmail.com writes:

 Luis Anaya papoan...@hotmail.com writes:

 Eric Schulte eric.schu...@gmx.com writes:

 Hi,

 Maybe I'm missing something obvious here, but I can't get org-e-groff to
 generate anything but an empty output file.  I've boiled this down to

 Hi:

 No, you're not missing something, there's is a problem. I just ran
 regression and all the groff files are empty. My gut feeling is the
 change from the defvar to the invocation of
 `org-export-define-backend' is not mapping the different calls to
 its respective function. First thing I noticed is that the second
 parameter, is a symbol while the function expects it to be a string
 (it's passing it into a format), that may be one of the problems. I
 changed it to a string with the same results. (i. e. empty files).


 I ran it with an older version of org-e-groff.el that does not use 
 this function and it runs fine with the lastest from git.  

 Hmmm...

This is because I made a typo when defining the back-end: there
shouldn't be any quote before the first alist.


Regards,

-- 
Nicolas Goaziou

Re: [O] LaTeX export problem

[Nicolas Goaziou]

Hello,

Alexander Vorobiev alexander.vorob...@gmail.com writes:

 I tried the new exporter (using today's snapshot of the sources) and
 it produced invalid LaTeX (it calls hypersetup without loading
 hyperref package).

The export back-end doesn't load any package on its own. You have to
make sure hyperref is properly loaded (AFAIK, it is by default).

 It also ignored the #+LaTeX_CLASS: and all the
 #+LaTeX_HEADER:lines in my file.

Those lines shouldn't be ignored. You probably don't have any matching
entry in `org-e-latex-classes' for your #+LATEX_CLASS: specification.

I'm not sure about #+LaTeX_HEADER: lines. Do you have an example?

 Are there any examples of org files which show how to customize the
 new LaTeX exporter?

Try first:

M-x customize-group RET org-export-e-latex RET


Regards,

-- 
Nicolas Goaziou

Re: [O] Invalid function: with-parsed-tramp-file-name with Perl

[Bastien]

Achim Gratz strom...@nexgo.de writes:

 Bastien writes:
 Can you summarize what would be the change and why it is called for?

 The tag release_7.8.11 is affixed to the merge commit, which means that
 it's first parent is on the master branch rather than maint.  The change
 sets it back one commit so that it correctly is located on the maint
 branch.

Okay, thanks.

 We'll have to tell users to forcibly update the tags again.

For the users who will not do this, only the release_7.8.11
will not properly set, right?

If so, you can go ahead with the change.

-- 
 Bastien

Re: [O] babel for ditaa-eps

[Bastien]

Hi Thomas,

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

 Is it possible to distribute DitaaEps.jar with Org?  Or, does it need to
 be installed separately?

I just wrote to the ditaa author.

Arne told me ditaaeps works with ditaa 0.6b but not with latest 
ditaa 0.9, the one we are distributing.  I don't want to distribute
several versions of ditaa in Org mode, so I ask the ditaa author
to see if he can make ditaaeps work with latest ditaa.

I'll let you know, best,

-- 
 Bastien

Re: [O] Problem with org-entities-user

[Nicolas Goaziou]

Hello,

Carsten Dominik carsten.domi...@gmail.com writes:

 The only thing is:  I do use Org to draft documents intended to
 be later fine-tuned as LaTeX documents, while I don't usually
 do this for other backends.  So the ability to put in naked
 LaTeX formatting commands does have value and convenience for
 me personally.

If the LaTeX command doesn't require an argument, you can always add it
to `org-entities-user'. Otherwise, you may define a macro like the
following:

  #+MACRO: sc @@e-latex:\textsc{@@$1@@e-latex:}@@

I agree that's not as convenient to set up. But once it is done, it's as
easy to use as raw commands.

Anyway this is a minor point. I guess it will be swept under the rug of
historical reasons, after all.


Regards,

-- 
Nicolas Goaziou

Re: [O] An org-attach link type [7.9.1 (7.9.1-elpa @ /home/youngfrog/.emacs.d/elpa/org-20120903/)]

[Nicolas Richard]

Hello Viktor,

Thanks for your input.

 - I have to load the cl module, otherwise the case function is
 void.

Sorry about that. I didn't notice it was from cl.

 - I had to replace find-lisp-find-files with directory-files because
   the former does not exist on my Emacs installation. I use GNU Emacs
   24.2.1 on OS X compiled from MacPorts.

Oops again. (require 'find-lisp) should fix that. The big difference
with directory-files is that find-lisp-find-files looks also in
subdirectories (I often attach subdirectories and like to link files
from therein). And it returns full paths, too, which explains some parts
of the rest of the code. 

 - I use attach instead of att as a link prefix in my files and had
   to change the names of the functions. Sorry about that, but I did not
   want to fix all my links.

That's fine, I only used att because it was the name I found in an
older discussion and I just copied the code.

-- 
Nico.

Re: [O] org-e-groff-export-to-groff produces empty output file

[Luis Anaya]

Yes, that happens. :)If it's taken care of and push to git, I can go ahead and run regression to make sure that everything is working ok. Luis Original Message  From: Nicolas Goaziou  Sent: Sat, Sep 22, 2012 03:55 AM To: Luis Anaya  CC: Eric Schulte ; Org Mode Mailing List  Subject: Re: org-e-groff-export-to-groff produces empty output fileHello,

Luis Anaya  writes:

> Luis Anaya  writes:
>
>> Eric Schulte  writes:
>>
>>> Hi,
>>>
>>> Maybe I'm missing something obvious here, but I can't get org-e-groff to
>>> generate anything but an empty output file.  I've boiled this down to
>
> Hi:
>
> No, you're not missing something, there's is a problem. I just ran
> regression and all the groff files are empty. My gut feeling is the
> change from the defvar to the invocation of
> `org-export-define-backend' is not mapping the different calls to
> its respective function. First thing I noticed is that the second
> parameter, is a symbol while the function expects it to be a string
> (it's passing it into a format), that may be one of the problems. I
> changed it to a string with the same results. (i. e. empty files).
>
>
> I ran it with an older version of org-e-groff.el that does not use 
> this function and it runs fine with the lastest from git.  
>
> Hmmm...

This is because I made a typo when defining the back-end: there
shouldn't be any quote before the first alist.


Regards,

-- 
Nicolas Goaziou

Re: [O] Visibility cycling with inline tasks

[Bastien]

Hi Carsten,

Carsten Dominik carsten.domi...@gmail.com writes:

 I agree that this would be a good default, but not with a hard-coded 6.

 (add-hook 'org-cycle-hook
  (lambda (state) (when (eq state 'contents)
  (and (boundp 'org-inlinetask-min-level)
   org-inlinetask-min-level
   (hide-sublevels (1- org-inlinetask-min-level))


 And it is probably better to wrap this into a function and add that function
 to the default value of org-cycle-hook, after org-cucle-hide-drawers

Done in master.  Thanks!

-- 
 Bastien

Re: [O] Visibility cycling with inline tasks

[Carsten Dominik]

GReat, thanks!

- Carsten

On 22.9.2012, at 11:02, Bastien wrote:

 Hi Carsten,
 
 Carsten Dominik carsten.domi...@gmail.com writes:
 
 I agree that this would be a good default, but not with a hard-coded 6.
 
 (add-hook 'org-cycle-hook
 (lambda (state) (when (eq state 'contents)
 (and (boundp 'org-inlinetask-min-level)
  org-inlinetask-min-level
  (hide-sublevels (1- org-inlinetask-min-level))
 
 
 And it is probably better to wrap this into a function and add that function
 to the default value of org-cycle-hook, after org-cucle-hide-drawers
 
 Done in master.  Thanks!
 
 -- 
 Bastien

Re: [O] org-e-groff-export-to-groff produces empty output file

[Nicolas Goaziou]

Hello,

Luis Anaya papoan...@hotmail.com writes:

 If it's taken care of and push to git, I can go ahead and run
 regression to make sure that everything is working ok.

Unfortunately, I don't seem to have push access to repository for now.
It will either have to be done by someone else or wait until I can fix
it.

For the record, it's just about removing the quote at the beginning of
the line 51 in org-e-groff.el.

You may also want to remove the two `defvar' above, which look useless.


Regards,

-- 
Nicolas Goaziou

Re: [O] org-capture-template suspicious behaviour of expansion elements

[Bastien]

Hi Myles,

Myles English mylesengl...@gmail.com writes:

 Using the git repo, I am fairly sure that one of my capture templates
 stopped working sometime in the last few weeks, no so much as to warrant
 a bug report but thought I would point it out as it may be unintended or
 part of a bigger picture:

 #+begin_src elisp
 (setq org-capture-templates (quote (
   (t   - test entry
   (file test.org) * %? \n%^t%U
 #+end_src elisp
   \n%^t %U
^
 that space is important now, otherwise the %^t is not
expanded.

This is now fixed, thanks.

-- 
 Bastien

Re: [O] An org-attach link type [7.9.1 (7.9.1-elpa @ /home/youngfrog/.emacs.d/elpa/org-20120903/)]

[Bastien]

Hi Nicolas,

I pushed a slightly modified version of your patch in master.

Thanks for this!

If you feel like adding the attach link type to org-attach.el
please go ahead and provide a patch.  Beware of the format of
the patch, though: it must contain a proper ChangeLog.  See

  http://orgmode.org/worg/org-contribute.html#sec-5

for more details.

Thanks in advance!

-- 
 Bastien

Re: [O] org-metaup / org-metadown nerfed in 7.9.1

[Bastien]

Hi Anthony,

Anthony Lander anth...@landerfamily.ca writes:

 I use the M-up/dn behaviour a lot to move property lines up and down.

Maybe each property line could be a new element recognized as such by
org-element.el.  This way org-metaup/down on a property line would move
it up/down.

(Maybe there are some other benefits from having such an element, 
but I'll trust Nicolas on this.)

Nicolas, what do you think?

-- 
 Bastien

Re: [O] org-e-groff-export-to-groff produces empty output file

[Luis Anaya]

Hi:I can remove and push it (if allowed). I know that there was a change in the server being that git complained about the SSL certificate. I'll keep you posted. Luis Original Message  From: Nicolas Goaziou  Sent: Sat, Sep 22, 2012 05:03 AM To: Luis Anaya  CC: Org Mode Mailing List ; Eric Schulte  Subject: Re: org-e-groff-export-to-groff produces empty output fileHello,

Luis Anaya  writes:

> If it's taken care of and push to git, I can go ahead and run
> regression to make sure that everything is working ok.

Unfortunately, I don't seem to have push access to repository for now.
It will either have to be done by someone else or wait until I can fix
it.

For the record, it's just about removing the quote at the beginning of
the line 51 in org-e-groff.el.

You may also want to remove the two `defvar' above, which look useless.


Regards,

-- 
Nicolas Goaziou

Re: [O] org-e-groff-export-to-groff produces empty output file

[Nicolas Goaziou]

Hello,

Luis Anaya papoan...@hotmail.com writes:

 I can remove and push it (if allowed). I know that there was a change
 in the server being that git complained about the SSL certificate.

I've regained push access. So it should be fixed now. I let you
double-check the commits.

As a side note, there was a typo in some element types (latex-fragment
and latex-environment) so they were ignored by the Groff back-end. I've
fixed their name, but, since I don't know what you want to do with them,
I've commented them out from back-end definition. Thus, they are still
ignored (see lines 68-69 in the file). I let you decide what to do with
them.


Regards,

-- 
Nicolas Goaziou

Re: [O] org-e-groff-export-to-groff produces empty output file

[Luis Anaya]

Nicolas:I think that we commited at the same time. Git warned me about it and I got the conflicts resolved. I checked the file in the Org Git repository, it looks fine.  I'm running regression and well, no empty files. :)Luis Original Message  From: Nicolas Goaziou  Sent: Sat, Sep 22, 2012 05:03 AM To: Luis Anaya  CC: Org Mode Mailing List ; Eric Schulte  Subject: Re: org-e-groff-export-to-groff produces empty output fileHello,

Luis Anaya  writes:

> If it's taken care of and push to git, I can go ahead and run
> regression to make sure that everything is working ok.

Unfortunately, I don't seem to have push access to repository for now.
It will either have to be done by someone else or wait until I can fix
it.

For the record, it's just about removing the quote at the beginning of
the line 51 in org-e-groff.el.

You may also want to remove the two `defvar' above, which look useless.


Regards,

-- 
Nicolas Goaziou

Re: [O] suggestion for org-emphasis-regexp-components: *U*nited *N*ations

[Bastien]

Hi Stefan,

Stefan Vollmar voll...@nf.mpg.de writes:

 It is possible to use the same trick that Łukasz Stelmach mentioned in
 the context of = markers in 2010:

This trick might be useful to others -- could someone add this to the
org-faq.org?

Thanks!

-- 
 Bastien

Re: [O] org-e-groff-export-to-groff produces empty output file

[Luis Anaya]

Hi:When I commited that returned the conflict warning, I noticed that they were removed. I cannot think of a use for those while typesetting in Groff, other than send Groff commands with a LaTeX instruction (awkward...).  If this is the case, those two routines should be removed from the exporter as well.Luis Original Message  From: Nicolas Goaziou  Sent: Sat, Sep 22, 2012 05:32 AM To: Luis Anaya  CC: Org Mode Mailing List ; Eric Schulte  Subject: Re: org-e-groff-export-to-groff produces empty output fileHello,

Luis Anaya  writes:

> I can remove and push it (if allowed). I know that there was a change
> in the server being that git complained about the SSL certificate.

I've regained push access. So it should be fixed now. I let you
double-check the commits.

As a side note, there was a typo in some element types (latex-fragment
and latex-environment) so they were ignored by the Groff back-end. I've
fixed their name, but, since I don't know what you want to do with them,
I've commented them out from back-end definition. Thus, they are still
ignored (see lines 68-69 in the file). I let you decide what to do with
them.


Regards,

-- 
Nicolas Goaziou

Re: [O] Invalid function: with-parsed-tramp-file-name with Perl

[Achim Gratz]

Bastien writes:
 We'll have to tell users to forcibly update the tags again.

 For the users who will not do this, only the release_7.8.11
 will not properly set, right?

Yes.  Another sticky point is that any clones of the orgmode repo (like
the one on repo.or.cz) will not automatically pick that change up as
well.

 If so, you can go ahead with the change.

Done.


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

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables

Re: [O] org-e-groff-export-to-groff produces empty output file

[Nicolas Goaziou]

Luis Anaya papoan...@hotmail.com writes:

 I cannot think of a use for those while typesetting in Groff, other
 than send Groff commands with a LaTeX instruction (awkward...). If
 this is the case, those two routines should be removed from the
 exporter as well.

`e-html' back-end turns them into images (with, i.e. dvipng). Would that
be applicable to Groff as well?

Regards,

Re: [O] [OT] Current website not very attractive

[John Hendy]

For firewalls (im behind one too) see if theres an https alternative. I
guess you solved this, but some might not be able to futz with proxies (or
shouldn't) at work :)
On Sep 21, 2012 5:50 PM, Nick Dokos nicholas.do...@hp.com wrote:

 Marcelo de Moraes Serpa celose...@gmail.com wrote:

  Bastien,
 
  I can't clone the orgweb repo:
 
  git clone git://orgmode.org/orgweb.git
  Cloning into 'orgweb'...
  fatal: The remote end hung up unexpectedly
 
  Is the server is down?
 

 I can't get to it either, but I am behind a firewall and have had
 problems with the socks proxy I usually use. After I switched proxies,
 I *was* able to do a git pull on the emacs repository though, so I
 suspect the fault is at orgmode.org's end.

 Nick

  - Marcelo.
 
  On Fri, Sep 14, 2012 at 12:41 AM, Bastien b...@altern.org wrote:
 
  Hi Marcelo,
 
  glad you like the new website!  It's important to keep Org open
  to non-developers, it is good if the website somehow advertizes
  this attitude.
 
  Marcelo de Moraes Serpa celose...@gmail.com writes:
 
   I can help with the Spanish and Portuguese versions, by the way.
 
  Great!
 
  ~$ git clone git://orgmode.org/orgweb.git
  ~$ cd orgweb/
  ~$ git branch orgweb-es
  ~$ mkdir es/
  ~$ cp *org es/
 
  [translate the es/*org files]
 
  ~$ git commit -m Yeah! es translation done!
  ~$ git format-patch master
 
  ... then send me the patch(es).
 
  Should be one-hour max of work.
 
  Thanks in advance :)
 
  --
   Bastien
 
 
  
  Alternatives:
 
  

Re: [O] [OT] Current website not very attractive

[Achim Gratz]

Bastien writes:
 I think Jason is not online this week-end, so we will have to
 live with it.

He has just fixed it and it works again with my old configuration.


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

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

Re: [O] org-wikinodes - is there a limit of processable files/nodes

[Marcelo de Moraes Serpa]

Hi Bastien,

Working now, thanks a lot! What was that change about?

One last question:

How can I have a wikilink in a headline? When I write a CamelCased link in
an org headline, it doesn't get converted to a link automatically, probably
because headlines are the nodes and that might cause a deadlock loop? Is
there a way to force a wikilink (to another wikinode) in a headline? (I've
tried enclosing in [[]] but it doesn't seem to create a wikinode link, only
a regular org link).

Also, a suggestion: I think an additional value for the scope setting could
be created called list of directories, where you could force a specific
directory(ies) where you keep your wiki org files. Right now, I'm doing
that by modifying the function as I stated in the previous message. I might
do that if I have the time, but I fear breaking something else, as my elisp
skills are still quite basic.

Cheers,

Marcelo.

On Sat, Sep 22, 2012 at 2:21 AM, Bastien b...@altern.org wrote:

 Hi Marcelo,

 Marcelo de Moraes Serpa celose...@gmail.com writes:

  Why? Because I have files in other directory levels that I still want
  to link to the wiki, so basically I want to force all wikilinks to
  point to nodes in org files that reside in this wiki/ directory only.

 I just pushed some changes in org-wikinodes.el, maybe they will solve
 your problem.  Let me know.

 Thanks,

 --
  Bastien

Re: [O] Problem with org-entities-user

[Carsten Dominik]

On 22.9.2012, at 10:52, Nicolas Goaziou wrote:

 Hello,
 
 Carsten Dominik carsten.domi...@gmail.com writes:
 
 The only thing is:  I do use Org to draft documents intended to
 be later fine-tuned as LaTeX documents, while I don't usually
 do this for other backends.  So the ability to put in naked
 LaTeX formatting commands does have value and convenience for
 me personally.
 
 If the LaTeX command doesn't require an argument, you can always add it
 to `org-entities-user'.

Yes, even though this is not very clean by itself.

 Otherwise, you may define a macro like the
 following:
 
  #+MACRO: sc @@e-latex:\textsc{@@$1@@e-latex:}@@
 
 I agree that's not as convenient to set up. But once it is done, it's as
 easy to use as raw commands.

True.

 
 Anyway this is a minor point. I guess it will be swept under the rug of
 historical reasons, after all.

Maybe not.  I can go along with your arguments for cleanness.  Would you object 
to keeping this feature in as an option, turned off be default, so that it is 
at least easy to keep lengthy files working?

The way I understand it, the new exporter will be default in 8.0, so this is 
the time to make some incompatible changes.  But if it is possible to support 
this as an option, I would like it.

Regards

- Carsten

Re: [O] Invalid function: with-parsed-tramp-file-name with Perl

[Bastien]

Achim Gratz strom...@nexgo.de writes:

 Bastien writes:
 We'll have to tell users to forcibly update the tags again.

 For the users who will not do this, only the release_7.8.11
 will not properly set, right?

 Yes.  Another sticky point is that any clones of the orgmode repo (like
 the one on repo.or.cz) will not automatically pick that change up as
 well.

I contacted the repo.or.cz for this, thanks.

 If so, you can go ahead with the change.

 Done.

Thanks!

-- 
 Bastien

Re: [O] [PATCH] org-insert-link: allow ido usage when inserting links

[Bastien]

Hi Tony,

tony day zygom...@gmail.com writes:

 [PATCH] org-insert-link: allow ido usage when inserting links

I'm now marking this patch as not applicable in the patchwork,
and I've archived it.  Please resend it when the FSF papers are
in order.  

Also double-check the formatting of the ChangeLog entry: use 
the active voice, start sentences with an uppercase letter, end 
it with a . and use two spaces after each... then you'll have
the perfect patch :)

Thanks!

-- 
 Bastien

[O] New LaTeX exporter, Invalid search bound

[Thomas S. Dye]

Aloha all,

A document that exported nicely with the new LaTeX exporter on 9/18 now
fails with a more recent pull from git. I've included a portion of the
backtrace and the section of the org file that triggers the error.

Org-mode version 7.9.1 (release_7.9.1-299-g08c5ea @ 
/Users/dk/.emacs.d/src/org-mode/lisp/)

Here is the (hopefully) relevant portion of the (really large) backtrace:

Debugger entered--Lisp error: (error Invalid search bound (wrong side of 
point))
  re-search-forward(^\\(?:\\*+ \\|\\[\\(?:[0-9]+\\|fn:[-_[:word:]]+\\)\\]\\|[  
]*\\(?:$\\|\\(?:|\\|\\+-[-+]\\)\\|[#:]\\|-\\{5,\\}[ 
]*$\\|begin{\\([A-Za-z0-9]+\\*?\\)}\\|\\(?:\\(?:CLO\\(?:CK\\|SED\\)\\|DEADLINE\\|SCHEDULED\\):\\)\\|\\(?:[-+*]\\|\\(?:[0-9]+\\)[.)]\\)\\(?:[
]\\|$\\)\\)\\) 67425 m)
  org-element-paragraph-parser(67425 (67425 :name 
define-biblatex-footcitetext-link))
  org-element--current-element(67425 nil nil nil)
  org-element--parse-elements(67149 67425 nil nil nil nil (section (:begin 
67149 :end 67425 :contents-begin 67149 :contents-end 67425 :post-blank 0)))
  org-element--parse-elements(67149 67425 section nil nil nil (headline 
(:raw-value Standard Biblatex citation commands :begin 67109 :end 67425 
:pre-blank 1 :hiddenp outline :contents-begin 67149 :contents-end 67425 :level 
2 :priority nil :tags nil :todo-keyword nil :todo-type nil :scheduled nil 
:deadline nil :timestamp nil :clock nil :post-blank 1 :footnote-section-p nil 
:archivedp nil :commentedp nil :quotedp nil :category ??? :title (Standard 
Biblatex citation commands


Here is the section of the org file that triggers the error:
 
** Standard Biblatex citation commands

#+name: define-standard-biblatex-commands
#+begin_src emacs-lisp :noweb yes :results silent :exports none
  define-biblatex-cite-link
  define-biblatex-cap-cite-link
  define-biblatex-parencite-link
  define-biblatex-cap-parencite-link
  define-biblatex-footcite-link
  define-biblatex-footcitetext-link

#+end_src

#+name: define-biblatex-cite-link
#+begin_src emacs-lisp :results silent :exports none
  (org-add-link-type 
   cite 'ebib
   (lambda (path desc format)
 (cond
  ((eq format 'html)
   (format (cite%s/cite) path))
  ((eq format 'latex)
   (if (or (not desc) (equal 0 (search cite: desc)))
   (format \\cite{%s} path)
 (format \\cite[%s][%s]{%s}
 (cadr (split-string desc ;))
 (car (split-string desc ;))  path))
#+end_src

#+name: define-biblatex-cap-cite-link
#+begin_src emacs-lisp :results silent :exports none
  (org-add-link-type 
   Cite 'ebib
   (lambda (path desc format)
 (cond
  ((eq format 'html)
   (format (cite%s/cite) path))
  ((eq format 'latex)
   (if (or (not desc) (equal 0 (search Cite: desc)))
   (format \\Cite{%s} path)
 (format \\Cite[%s][%s]{%s}
 (cadr (split-string desc ;))
 (car (split-string desc ;))  path))
#+end_src

#+name: define-biblatex-parencite-link
#+begin_src emacs-lisp :results silent :exports none
  (org-add-link-type 
   parencite 'ebib
   (lambda (path desc format)
 (cond
  ((eq format 'html)
   (format (cite%s/cite) path))
  ((eq format 'latex)
   (if (or (not desc) (equal 0 (search parencite: desc)))
   (format \\parencite{%s} path)
 (format \\parencite[%s][%s]{%s}
 (cadr (split-string desc ;))
 (car (split-string desc ;))  path))
#+end_src

#+name: define-biblatex-cap-parencite-link
#+begin_src emacs-lisp :results silent :exports none
  (org-add-link-type 
   Parencite 'ebib
   (lambda (path desc format)
 (cond
  ((eq format 'html)
   (format (cite%s/cite) path))
  ((eq format 'latex)
   (if (or (not desc) (equal 0 (search Parencite: desc)))
   (format \\Parencite{%s} path)
 (format \\Parencite[%s][%s]{%s}
 (cadr (split-string desc ;))
 (car (split-string desc ;))  path))
#+end_src

#+name: define-biblatex-footcite-link
#+begin_src emacs-lisp :results silent :exports none
  (org-add-link-type 
   footcite 'ebib
   (lambda (path desc format)
 (cond
  ((eq format 'html)
   (format (cite%s/cite) path))
  ((eq format 'latex)
   (if (or (not desc) (equal 0 (search footcite: desc)))
   (format \\footcite{%s} path)
 (format \\footcite[%s][%s]{%s}
 (cadr (split-string desc ;))
 (car (split-string desc ;))  path))
#+end_src

#+name: define-biblatex-footcitetext-link
#+begin_src emacs-lisp :results silent :exports none
  (org-add-link-type 
   footcitetext 'ebib
   (lambda (path desc format)
 (cond
  ((eq format 'html)
   (format (cite%s/cite) path))
  ((eq format 'latex)
   (if (or (not desc) (equal 0 (search footcitetext: desc)))
   (format \\footcitetext{%s} path)
 (format \\footcitetext[%s][%s]{%s}
 (cadr (split-string desc ;))
 

Re: [O] org-wikinodes - is there a limit of processable files/nodes

[Bastien]

Hi Marcelo,

Marcelo de Moraes Serpa celose...@gmail.com writes:

 How can I have a wikilink in a headline?

I think you cannot, as the goal of a wikilink is to jump to a headline.

 When I write a CamelCased
 link in an org headline, it doesn't get converted to a link
 automatically, probably because headlines are the nodes and that
 might cause a deadlock loop? 

Indeed.

 Is there a way to force a wikilink (to
 another wikinode) in a headline? (I've tried enclosing in [[]] but it
 doesn't seem to create a wikinode link, only a regular org link).

I don't know if Carsten is using org-wikinodes.el (?) but I'm pretty
sure you can start hacking it.  A nice playground for discovering both
lisp and Org!

 Also, a suggestion: I think an additional value for the scope setting
 could be created called list of directories, where you could force
 a specific directory(ies) where you keep your wiki org files. Right
 now, I'm doing that by modifying the function as I stated in the
 previous message. I might do that if I have the time, but I fear
 breaking something else, as my elisp skills are still quite basic.

A nice little feature to add, it should not be difficult.

Let us know how it goes!

-- 
 Bastien

Re: [O] New exporter: no custom timestamps

[Bastien]

Hi Nicolas,

Nicolas Goaziou n.goaz...@gmail.com writes:

 What do you think?

I think it would be great!

-- 
 Bastien

Re: [O] New exporter: no custom timestamps

[Bastien]

Hi Jambunathan,

Bastien b...@altern.org writes:

 I suggest to fix this in org-e-html.el with the attached patch.

I have now applied the patch.  

Feel free to amend/edit/revert it if you think it is not good.

Thanks Giovanni for reporting this.

-- 
 Bastien

Re: [O] Problem with org-entities-user

[Thomas S. Dye]

Carsten Dominik carsten.domi...@gmail.com writes:

 On 22.9.2012, at 10:52, Nicolas Goaziou wrote:

 Hello,
 
 Carsten Dominik carsten.domi...@gmail.com writes:
 
 The only thing is:  I do use Org to draft documents intended to
 be later fine-tuned as LaTeX documents, while I don't usually
 do this for other backends.  So the ability to put in naked
 LaTeX formatting commands does have value and convenience for
 me personally.
 
 If the LaTeX command doesn't require an argument, you can always add it
 to `org-entities-user'.

 Yes, even though this is not very clean by itself.

 Otherwise, you may define a macro like the
 following:
 
  #+MACRO: sc @@e-latex:\textsc{@@$1@@e-latex:}@@
 
 I agree that's not as convenient to set up. But once it is done, it's as
 easy to use as raw commands.

 True.

 
 Anyway this is a minor point. I guess it will be swept under the rug of
 historical reasons, after all.

 Maybe not. I can go along with your arguments for cleanness. Would you
 object to keeping this feature in as an option, turned off be default,
 so that it is at least easy to keep lengthy files working?

 The way I understand it, the new exporter will be default in 8.0, so
 this is the time to make some incompatible changes. But if it is
 possible to support this as an option, I would like it.

 Regards

 - Carsten


I would like this, too. I think it would help me keep reproducible
research documents viable.

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] An org-attach link type [7.9.1 (7.9.1-elpa @ /home/youngfrog/.emacs.d/elpa/org-20120903/)]

[Viktor Rosenfeld]

Hi Nicolas,

Nicolas Richard wrote:

 Hello Viktor,
 
 Thanks for your input.
 
  - I have to load the cl module, otherwise the case function is
  void.
 
 Sorry about that. I didn't notice it was from cl.
 
  - I had to replace find-lisp-find-files with directory-files because
the former does not exist on my Emacs installation. I use GNU Emacs
24.2.1 on OS X compiled from MacPorts.
 
 Oops again. (require 'find-lisp) should fix that. The big difference
 with directory-files is that find-lisp-find-files looks also in
 subdirectories (I often attach subdirectories and like to link files
 from therein). And it returns full paths, too, which explains some parts
 of the rest of the code. 

If find-lisp-find-files returns full paths then the discrimination in
org-attach-complete-how makes sense. Pretty cool.

Cheers,
Viktor

Re: [O] Sending commits to Org

[Jarmo Hurri]

Philipp Kroos philipp.kr...@t-online.de writes:

 If you first create a branch on your side and switch to it before
 making changes, you can run format-patch against your local copy of
 master as well.

Or, if you are a git newbie like me, and fail to read the relevant part
of the org page on contributing, and make your changes in the original
master, you can also create patches from the original master branch
using the HEAD identifier. For example,

git format-patch HEAD~1

gives you a patch of the last commita. If, after having made your changes
in the master branch, a pull has resulted in newer changes, you can
create more patches by increasing the argument to head. For example,
currently I need to run

git format-patch HEAD~3

to re-create a patch of my own, local changes. I hope (?) this patch is
as good as one that would be created by having my own branch.

Sorry if the terminology is a bit mixed, but as I said, I am a git
newbie. (As a long-time CVS user I would need to reserve some time to
study the manual...)

--
Jarmo

Re: [O] org-e-groff-export-to-groff produces empty output file

[Luis Anaya]

Nicolas Goaziou n.goaz...@gmail.com writes:

 `e-html' back-end turns them into images (with, i.e. dvipng). Would that
 be applicable to Groff as well?

Hmm... that's an idea... It would be useful for equations. Even though
Groff has EQN, if you're used to LaTeX ones, you do not have to learn
another set. 

The only difference that it has to be exported with dvips, but at the
end is just the same difference.

Let me look at the html code and see. :)

Luis


-- 
Luis Anaya
papo anaya aroba hot mail punto com
Do not use 100 words if you can say it in 10 - Yamamoto Tsunetomo

Re: [O] org-e-groff-export-to-groff produces empty output file

[Luis Anaya]

Luis Anaya papoan...@hotmail.com writes:

 An HTML attachment was scrubbed...
 URL: 
 http://lists.gnu.org/archive/html/emacs-orgmode/attachments/20120922/5b696f1b/attachment.html

... great, this is what happens when I send email from my phone
:(. Sorry about that. 

Luis

-- 
Luis Anaya
papo anaya aroba hot mail punto com
Do not use 100 words if you can say it in 10 - Yamamoto Tsunetomo

[O] Bug: ob.R sets ess-ask-for-ess-directory to a wrong value [7.8.03 (release_7.9.1.301.g1fea5)]

[Vitalie Spinu]

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, 

Can please this variable

╭ #203 ─ org-mode/lisp/ob-R.el ──
│ 
│ (defvar ess-ask-for-ess-directory nil)
╰ #204 ─

be set to t?

This is a custom variable in ESS and is by default t. If org is loaded
before ESS the variable is set to a wrong value.

Thanks, 
Vitalie


Emacs  : GNU Emacs 24.2.50.1 (i686-pc-linux-gnu, GTK+ Version 3.4.2)
 of 2012-09-19 on dryad, modified by Debian
Package: Org-mode version 7.8.03 (release_7.9.1.301.g1fea5)

Re: [O] Org HTML-PDF publishing

[Srinivas]

There is a free license for non-commerical use:

From princexml.com:
We offer a free license for non-commercial use of Prince. 
This license adds a small logo to the first page of 
generated PDF files.

Will this work for you?