[O] Presentation on Org-mode at Dunkerque (France)

[Fabrice Niessen]

Hello,

Just to tell you that I will make a presentation on Org-mode during the LaTeX
day in Dunkerque (FR) on Wed 13th June 2012.

Here is my summary in English for the 1:30 presentation:

You wish to write high-quality documents or presentations, whose
successive versions are easy to compare (thanks to CVS, SVN or Git, for
example)? LATEX is un-miss-able.

You find, nevertheless, the syntax very heavy to write tables or to handle
nested lists? You have problems convincing your colleagues to go the LaTeX
route?

Come then discover org-mode (http://orgmode.org/). Writing a document or a
presentation will become as simple as an writing an email. And you inherit
new possibilites (of which outlining, status and tags on the sections, as
well as the advanced search functions are some examples that will be
looked at).

It will be more focused to the LaTeX exporter, of course, but I will try to
give more incentive for making the switch!

My slides will be publicly available (first in French, in English as well if
these are judged as worthing it ;-)).

For subscribing to the event (limited to 100 seats), see details at:

http://stage-latex-gte.univ-littoral.fr/

Best regards,
Fabrice

-- 
Fabrice Niessen

Re: [O] [Feature Request] org-mobile edit:add nodes

[Henning Weiss]

Hi,

On Tue, Apr 24, 2012 at 1:08 AM, Bastien  wrote:

> Henning Weiss  writes:
>
> > it turns out that there are a couple of problems with that particular
> > patch. Some issues have already been fixed with the help of someone
> > else from the mobileorg community, but more work is required. As soon
> > as it is functional (and hopefully stable) I will post a new patch.
>
> Please do -- thanks for the follow up!
>
> --
>  Bastien
>

I have refined the edit nodes patch. Aaron Peromsik has helped me with
developing and testing it. He hasn't reported any problems with it and I
have been using it for a couple of weeks now without experiencing any
problems.

According to the contribution guidelines this patch doesn't qualify as a
TINYCHANGE. Assuming this patch qualifies for inclusion, do I need to fill
out the FSF copyright assignment form?

Henning


0001-org-mobile-Added-five-new-targets-for-edit-nodes.patch
Description: Binary data

Re: [O] Org-mode release 7.8.10

[Russell Adams]

Bastien & team,

I must applaud you once again. I just refreshed my setup, jumping from
7.01 to 7.8.10 and Org didn't skip a beat.

Fantastic work!

On Thu, May 17, 2012 at 12:04:31AM +0200, Bastien wrote:
> Hi folks,
>
> I released Org 7.8.10, a bugfix-only release.
>
>   http://orgmode.org/org-7.8.10.zip
>   http://orgmode.org/org-7.8.10.tar.gz
>   http://orgmode.org/org-mode-download.html
>
> This release will be the one in Emacs 24.1.
>
> (Mh.. Does it sound like I'm repeating myself?)
>
> As usual, enjoy!
>
> --
>  Bastien
>
>


--
Russell Adamsrlad...@adamsinfoserv.com

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

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

[O] makefile regression

[Greg Troxel]

For a long time, I've been updating org from git every week or two via:

  update-org () {
  (cd $HOME/SOFTWARE/EMACS/org-mode && git pull && make)
  }

and I have emacs pointed at that directory.   This is on NetBSD where
"make" is BSD make.

Today, I updated again and got:

  make: "/home/gdt/SOFTWARE/EMACS/org-mode/Makefile" line 6: Need an operator
  make: "/home/gdt/SOFTWARE/EMACS/org-mode/Makefile" line 87: Need an operator
  make: Fatal errors encountered -- cannot continue

  make: stopped in /home/gdt/SOFTWARE/EMACS/org-mode

and it seems recent changes have required beyond-POSIX-make features.

This seems unfortunate; I don't understand why building org has to be so
complicated.  If it is complicated, it seems best to use
autoconf/automake, which already have worked out most of the portability
issues.

At the very least a dependency on GNU make should be documented, if that
is indeed an intentional decision by the community.   (I haven't seen
any discussion, but I confess to not quite keeping up with with
emacs-orgmode traffic.)

Greg



pgpHzFWcj8zFH.pgp
Description: PGP signature

[O] breakage

[Nick Dokos]

Pulling just now I get:

,
| $ git checkout master
| Switched to branch 'master'
| Your branch is behind 'origin/master' by 15 commits, and can be 
fast-forwarded.
| 
| $ tsocks make update
| git remote update
| Fetching origin
| Fetching github
| Fetching org-odt
| git pull
| Updating 946230b..4721052
| Fast-forward
|  UTILITIES/org-fixup.el   |   66 ---
|  contrib/lisp/org-e-ascii.el  |   86 -
|  contrib/lisp/org-e-html.el   |7 +--
|  contrib/lisp/org-e-latex.el  |7 +--
|  contrib/lisp/org-e-odt.el|7 +--
|  contrib/lisp/org-element.el  |   16 +++---
|  contrib/lisp/org-export.el   |  111 ++---
|  default.mk   |   41 +++---
|  lisp/org-agenda.el   |4 +-
|  lisp/org-bbdb.el |2 +-
|  lisp/org-bibtex.el   |   14 +++---
|  lisp/org-clock.el|4 +-
|  lisp/org-exp.el  |2 +-
|  lisp/org-publish.el  |2 +-
|  lisp/org.el  |   37 +++--
|  targets.mk   |   10 ++--
|  testing/lisp/test-org-element.el |8 ++-
|  testing/lisp/test-org-export.el  |  109 +
|  18 files changed, 291 insertions(+), 242 deletions(-)
| make -C doc info
| make[1]: Entering directory `/home/nick/src/emacs/org/org-mode/doc'
| make[1]: Nothing to be done for `info'.
| make[1]: Leaving directory `/home/nick/src/emacs/org/org-mode/doc'
| make -C doc clean
| make[1]: Entering directory `/home/nick/src/emacs/org/org-mode/doc'
| rm -f org *.pdf *.html *_letter.tex org-version.inc \
| *.aux *.cp *.cps *.dvi *.fn *.fns *.ky *.kys *.pg *.pgs \
| *.toc *.tp *.tps *.vr *.vrs *.log *.html *.ps
| make[1]: Leaving directory `/home/nick/src/emacs/org/org-mode/doc'
| make -C doc all;  make -C etc all;  make -C lisp all;
| make[1]: Entering directory `/home/nick/src/emacs/org/org-mode/doc'
| org-version: 7.8.10 (release_7.8.10-582-g472105)
| makeinfo --no-split org.texi -o org
| make[1]: Leaving directory `/home/nick/src/emacs/org/org-mode/doc'
| make[1]: Entering directory `/home/nick/src/emacs/org/org-mode/etc'
| make[1]: Nothing to be done for `all'.
| make[1]: Leaving directory `/home/nick/src/emacs/org/org-mode/etc'
| make[1]: Entering directory `/home/nick/src/emacs/org/org-mode/lisp'
| rm -f org-version.el org-install.el org-version.elc org-install.elc
| org-version: 7.8.10 (release_7.8.10-582-g472105)
| Loading /home/nick/src/emacs/org/org-mode/lisp/org-compat.el (source)...
| Loading /home/nick/src/emacs/org/org-mode/UTILITIES/org-fixup.el (source)...
| Saving file /home/nick/src/emacs/org/org-mode/lisp/org-version.el...
| Loading vc-git...
| Wrote /home/nick/src/emacs/org/org-mode/lisp/org-version.el
| org-install: 7.8.10 (release_7.8.10-582-g472105)
| Loading /home/nick/src/emacs/org/org-mode/lisp/org-compat.el (source)...
| Loading /home/nick/src/emacs/org/org-mode/UTILITIES/org-fixup.el (source)...
| Wrong number of arguments: (lambda nil (with-temp-buffer 
(set-visited-file-name "org-install.el") (insert ";;; org-install.el --- 
autogenerated file, do not edit
| ;;
| ;;; Code:
| ") (let ((files (directory-files default-directory nil 
"^\\(org\\|ob\\)\\(-.*\\)?\\.el$"))) (mapc (lambda (f) (generate-file-autoloads 
f)) files)) (insert "
| (provide 'org-install)
| ") (insert "
| ;; Local Variables:
| ;; version-control: never
| ") (insert ";; no-byte-compile: t
| ;; no-update-autoloads: t
| ") (insert ";; coding: utf-8
| ;; End:
| ;;; org-install.el ends here
| ") (toggle-read-only 0) (save-buffer))), 1
| make[1]: *** [org-install.el] Error 255
| make[1]: Leaving directory `/home/nick/src/emacs/org/org-mode/lisp'
| make: *** [all] Error 2
| $
`


Nick

[O] How to get "Wrap at Window Edge" in org-mode?

[Marius Hofert]

Hi,

I am working with Xubuntu 12.04 on a MacBook Air (4,1) with org-mode version
7.8.09. I use the following code to get "Wrap at Window Edge" in
org-agenda-mode:

,
| (add-hook 'org-agenda-mode-hook
| '(lambda()
|(if truncate-lines (toggle-truncate-lines -1))
|))
`

How can I get "Wrap at Window Edge" in all .org files? The only idea I found is
https://plus.google.com/u/0/113859563190964307534/posts/RVBN7KvQtB7 but that
unfortunately did not work.

Cheers,

Marius

Re: [O] How to get "Wrap at Window Edge" in org-mode?

[Russell Adams]

On Tue, May 22, 2012 at 05:49:00PM +0200, Marius Hofert wrote:
> Hi,
>
> I am working with Xubuntu 12.04 on a MacBook Air (4,1) with org-mode version
> 7.8.09. I use the following code to get "Wrap at Window Edge" in
> org-agenda-mode:
>
> ,
> | (add-hook 'org-agenda-mode-hook
> |   '(lambda()
> |  (if truncate-lines (toggle-truncate-lines -1))
> |  ))
> `
>
> How can I get "Wrap at Window Edge" in all .org files? The only idea I found 
> is
> https://plus.google.com/u/0/113859563190964307534/posts/RVBN7KvQtB7 but that
> unfortunately did not work.
>
> Cheers,
>
> Marius
>

This will set wrapping globally from your .emacs file:

(setq-default truncate-lines nil)



--
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] README.org on github

[suvayu ali]

Hi Tom,

On Mon, May 21, 2012 at 3:29 PM, Tom Regner  wrote:
> Hi,
>
> suvayu ali  writes:
>
>> I see source blocks formated as example blocks. Is that the same as you
>> are seeing? If so, I wouldn't call that support for source blocks. I
>> would expect to see syntax highlighting like pure source files on
>> GitHub.
>
> org-ruby is in it's current form not capable to do that, but it's
> currently actively developed [fn:1] (maybe not for org-mode standards :-D, 
> the last
> commit was 8 days ago) and there are a few items on the todo list.
>
> And all shortcomings aside, an update on github/markups side would at
> least make the usage of org-documents on github bearable.
>

Sorry if my comments seemed like a complaint/gripe. When an org-mode
user says, "feature bla" is supported they usually mean the whole
thing, with all the bells and whistles (e.g. source block would imply
with syntax highlighting). So I just wanted to clarify it was
incorrect to say "source blocks are supported".

> Only sufficient demand for org-documents will foster betterment I guess.
>

Yes I realise that. I have never interacted with GitHub staff for
feature requests. Being a long time org-mode user (post-6.33, that's
ages in org years :-p), maybe I should give that a try.

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] README.org on github

[Puneeth Chaganti]

On Tue, May 22, 2012 at 9:24 PM, suvayu ali  wrote:
> Hi Tom,
>
> On Mon, May 21, 2012 at 3:29 PM, Tom Regner  wrote:
>> Hi,
>>
>> suvayu ali  writes:
>>
>>> I see source blocks formated as example blocks. Is that the same as you
>>> are seeing? If so, I wouldn't call that support for source blocks. I
>>> would expect to see syntax highlighting like pure source files on
>>> GitHub.
>>
>> org-ruby is in it's current form not capable to do that, but it's
>> currently actively developed [fn:1] (maybe not for org-mode standards :-D, 
>> the last
>> commit was 8 days ago) and there are a few items on the todo list.
>>
>> And all shortcomings aside, an update on github/markups side would at
>> least make the usage of org-documents on github bearable.
>>
>
> Sorry if my comments seemed like a complaint/gripe. When an org-mode
> user says, "feature bla" is supported they usually mean the whole
> thing, with all the bells and whistles (e.g. source block would imply
> with syntax highlighting). So I just wanted to clarify it was
> incorrect to say "source blocks are supported".

Yes, you are right.  Apologies for overlooking that.  But, this
feature shouldn't be too hard to add using albino or pygments.rb.  I
tried poking around org-ruby's code a little bit, but hit a roadblock,
which was a bit too much for my limited ruby skills.  I'll open an
issue on org-ruby and see where it goes.

>> Only sufficient demand for org-documents will foster betterment I guess.
>>
>
> Yes I realise that. I have never interacted with GitHub staff for
> feature requests. Being a long time org-mode user (post-6.33, that's
> ages in org years :-p), maybe I should give that a try.

I've tweeted to them at least a couple of times (in the past few
months) regarding this, but haven't yet got any response from them.
May be someone should send an email to supp...@github.com.  I got back
replies for other things in about a week or so, on email.  In general,
GitHub staff seem like a nice bunch of people to me.

Thanks!
Puneeth

Re: [O] How to get "Wrap at Window Edge" in org-mode?

[Marius Hofert]

Dear Russell,

I thought so, too, but it does not properly wrap standard .org files (including
sections etc.). Instead of Wrap at Window Edge, I still obtain "Truncate Long 
Lines"
mode in .org files.

Cheers,

Marius

Re: [O] makefile regression

[Bastien]

Hi Greg,

Greg Troxel  writes:

> For a long time, I've been updating org from git every week or two via:
>
>   update-org () {
>   (cd $HOME/SOFTWARE/EMACS/org-mode && git pull && make)
>   }
>
> and I have emacs pointed at that directory.   This is on NetBSD where
> "make" is BSD make.
>
> Today, I updated again and got:
>
>   make: "/home/gdt/SOFTWARE/EMACS/org-mode/Makefile" line 6: Need an operator
>   make: "/home/gdt/SOFTWARE/EMACS/org-mode/Makefile" line 87: Need an operator
>   make: Fatal errors encountered -- cannot continue
>
>   make: stopped in /home/gdt/SOFTWARE/EMACS/org-mode
>
> and it seems recent changes have required beyond-POSIX-make features.
>
> This seems unfortunate; I don't understand why building org has to be so
> complicated.  

It does *not* have to be.

> If it is complicated, it seems best to use
> autoconf/automake, which already have worked out most of the portability
> issues.
>
> At the very least a dependency on GNU make should be documented, if that
> is indeed an intentional decision by the community.   (I haven't seen
> any discussion, but I confess to not quite keeping up with with
> emacs-orgmode traffic.)

I will let Achim reply to your issue here.  I agree we should stick to
something as simple and portable as possible.  We will document all the
changes in this area for the 7.9 release.

Best,

-- 
 Bastien

Re: [O] breakage

[Bastien]

Hi Nick,

Nick Dokos  writes:

> | Loading /home/nick/src/emacs/org/org-mode/lisp/org-compat.el (source)...
> | Loading /home/nick/src/emacs/org/org-mode/UTILITIES/org-fixup.el (source)...
> | Wrong number of arguments: (lambda nil (with-temp-buffer
> | (set-visited-file-name "org-install.el") (insert ";;; org-install.el
> | --- autogenerated file, do not edit

Can you run (org-make-org-install) and perhaps instrument 
the function?

-- 
 Bastien

Re: [O] Org-mode release 7.8.10

[Bastien]

Russell Adams  writes:

> Bastien & team,
>
> I must applaud you once again. I just refreshed my setup, jumping from
> 7.01 to 7.8.10 and Org didn't skip a beat.
>
> Fantastic work!

Thanks!  

A team work really -- and glad to see old-timers still using Org :)

-- 
 Bastien

Re: [O] How to get "Wrap at Window Edge" in org-mode?

[Russell Adams]

The code segment you posed earlier with the lambda statement may
override that behavior. Have you tried removing that and restarting
emacs?

On Tue, May 22, 2012 at 06:14:07PM +0200, Marius Hofert wrote:
> Dear Russell,
>
> I thought so, too, but it does not properly wrap standard .org files 
> (including
> sections etc.). Instead of Wrap at Window Edge, I still obtain "Truncate Long 
> Lines"
> mode in .org files.
>
> Cheers,
>
> Marius
>


--
Russell Adamsrlad...@adamsinfoserv.com

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

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

[O] Comments break lists when exporting to TeX

[Daniel Schoepe]

Hi,

while trying to include a source file in a list element via #+INCLUDE, I
discovered the following behavior: A comment between two list elements breaks
the list into two lists when exporting. For example:

* Test
  - This is a list element.
# This isn't.
  - This is another list element.

Becomes after exporting to .tex:

..
\begin{itemize}
\item This is a list element.
\end{itemize}
\begin{itemize}
\item This is another list element.
\end{itemize}
..

I think it makes sense for comments to have no effect on this (i.e. it
should behave the same during export as if it wasn't there), so I
consider this a bug.

This has the unfortunate side effect of no longer being able to include
a source file using #+INCLUDE while preserving its indentation in the
resulting PDF (as using #+BEGIN_SRC .. #+END_SRC would).

Cheers,
Daniel


pgplkt0Ht9WTK.pgp
Description: PGP signature

Re: [O] How to get "Wrap at Window Edge" in org-mode?

[Marius Hofert]

Dear Russell,

thanks for helping.

Yes. I even removed ~/.emacs.desktop and restarted. Still, a standard 
.org file is shown in "Truncate Long Lines" mode instead of (the overall 
emacs default) "Wrap at Window Edge".


Cheers,

Marius


--
ETH Zurich
Dr. Marius Hofert
RiskLab, Department of Mathematics
HG E 65.2
Rämistrasse 101
8092 Zurich
Switzerland

Phone +41 44 632 2423
http://www.math.ethz.ch/~hofertj

Re: [O] How to get "Wrap at Window Edge" in org-mode?

[Bastien]

Hi Marius,

Marius Hofert  writes:

> I am working with Xubuntu 12.04 on a MacBook Air (4,1) with org-mode version
> 7.8.09. I use the following code to get "Wrap at Window Edge" in
> org-agenda-mode:
>
> ,
> | (add-hook 'org-agenda-mode-hook
> |   '(lambda()
> |  (if truncate-lines (toggle-truncate-lines -1))
> |  ))
> `
>
> How can I get "Wrap at Window Edge" in all .org files?

(setq org-startup-truncated nil)

HTH,

-- 
 Bastien

Re: [O] How to get "Wrap at Window Edge" in org-mode?

[Marius Hofert]

Hi Bastien,

Many thanks, that's exactly what I was looking for!

Cheers,

Marius

05/22/2012 07:21 PM, Bastien wrote:

Hi Marius,

Marius Hofert  writes:


I am working with Xubuntu 12.04 on a MacBook Air (4,1) with org-mode version
7.8.09. I use the following code to get "Wrap at Window Edge" in
org-agenda-mode:

,
| (add-hook 'org-agenda-mode-hook
| '(lambda()
|(if truncate-lines (toggle-truncate-lines -1))
|))
`

How can I get "Wrap at Window Edge" in all .org files?

(setq org-startup-truncated nil)

HTH,

Re: [O] [Feature Request] org-mobile edit:add nodes

[Bastien]

Hi Henning,

Henning Weiss  writes:

> I have refined the edit nodes patch. Aaron Peromsik has helped me
> with developing and testing it. He hasn't reported any problems with
> it and I have been using it for a couple of weeks now without
> experiencing any problems.

Thanks.  Can someone else test this patch?  I'm not using org-mobile.el.

> According to the contribution guidelines this patch doesn't qualify
> as a TINYCHANGE. Assuming this patch qualifies for inclusion, do I
> need to fill out the FSF copyright assignment form?

Yes, please do so.

Thanks,

-- 
 Bastien

Re: [O] Missing on worg

[Bastien]

Hi François,

François Pinard  writes:

> Page http://orgmode.org/worg/org-contrib/org-drill.html refers to
> inexisting http://orgmode.org/worg/org-contrib/spanish.html.  There is
> no spanish.org in the Org mode distribution either.  Maybe here?
>
>https://bitbucket.org/eeeickythump/org-drill/src/bc740455003b/spanish.org

Indeed, fixed.

Would you like to help us fix this by doing it yourself?

It's just a matter of sending me (or Jason) your public key,
we will then give your directions.

Thanks,

-- 
 Bastien

Re: [O] breakage

[Nick Dokos]

Bastien  wrote:

> Hi Nick,
> 
> Nick Dokos  writes:
> 
> > | Loading /home/nick/src/emacs/org/org-mode/lisp/org-compat.el (source)...
> > | Loading /home/nick/src/emacs/org/org-mode/UTILITIES/org-fixup.el 
> > (source)...
> > | Wrong number of arguments: (lambda nil (with-temp-buffer
> > | (set-visited-file-name "org-install.el") (insert ";;; org-install.el
> > | --- autogenerated file, do not edit
> 
> Can you run (org-make-org-install) and perhaps instrument 
> the function?
> 

I can't reproduce it any more - not sure what changed though.
To quote Emily Litella: ``Never mind...'' 

Nick

[O] stop comments and weblinks from being coloured and names of directories from being italised, /etc/

[Enda]

Can there be an #+OPTION to stop comments and weblinks from being coloured and 
names of directories from being italised, /etc/


Best wishes,

Enda

Re: [O] stop comments and weblinks from being coloured and names of directories from being italised, /etc/

[Nick Dokos]

Enda  wrote:

> Can there be an #+OPTION to stop comments and weblinks from being
> coloured and names of directories from being italised, /etc/
> 

In what context?

Nick

Re: [O] stop comments and weblinks from being coloured and names of directories from being italised, /etc/

[Bastien]

Nick Dokos  writes:

> Enda  wrote:
>
>> Can there be an #+OPTION to stop comments and weblinks from being
>> coloured and names of directories from being italised, /etc/
>
> In what context?

I guess the OP wants to hit M-x customize-face RET on comments and
links. 

2 cents,

-- 
 Bastien

Re: [O] stop comments and weblinks from being coloured and names of directories from being italised, /etc/

[Nick Dokos]

Bastien  wrote:

> Nick Dokos  writes:
> 
> > Enda  wrote:
> >
> >> Can there be an #+OPTION to stop comments and weblinks from being
> >> coloured and names of directories from being italised, /etc/
> >
> > In what context?
> 
> I guess the OP wants to hit M-x customize-face RET on comments and
> links. 
> 
> 2 cents,
> 

Maybe - but maybe he is talking about export. If I had a bit more time
and energy, I might have ranted about having to administer a third degree
interrogation in order to elicit the relevant information, but I don't
have either, so I won't :-) Guessing is all we can do at this point.

BTW, we now have four cents between us.

Nick

Re: [O] stop comments and weblinks from being coloured and names of directories from being italised, /etc/

[Bastien]

Nick Dokos  writes:

> BTW, we now have four cents between us.

Yes -- one day I'll count how much money has been spent in emails 
that never got answered back :)

-- 
 Bastien

Re: [O] stop comments and weblinks from being coloured and names of directories from being italised, /etc/

[Samuel Wales]

I think comments don't get exported, so it must be just regular Org?

-- 
The Kafka Pandemic: http://thekafkapandemic.blogspot.com

Re: [O] stop comments and weblinks from being coloured and names of directories from being italised, /etc/

[Bastien]

Samuel Wales  writes:

> I think comments don't get exported, so it must be just regular Org?

Indeed.  Hence my guess.

Thanks Samuel!  We spend cents, you spread wisdom :)

-- 
 Bastien

Re: [O] Language identifiers

[Bastien]

Hi François,

François Pinard  writes:

> A good way to study the
> new exporter's opinion would be for me to write a Python parser which
> yields exactly the same analysis.  That parser could usefully replace
> many Python scripts here which decipher Org files according to my mental
> fuzzy approximations of its syntax.

You can start from this existing python parser:
  http://members.optusnet.com.au/~charles57/GTD/orgnode.html

It's referenced here:
  http://orgmode.org/worg/org-tools/index.html

HTH,

-- 
 Bastien

Re: [O] Git mirrors

[Bastien]

Nick Dokos  writes:

> OTOH, some maintainers would prefer emailed patches instead;

FWIW, I prefer patches sent to this list for two reasons: they get
quickly tested by many people (i.e. faster than external branches) 
and bacause patches get caught on the patchwork.  Even if i don't
use the patchwork server to apply patches, I use it as a "watchlist".

-- 
 Bastien

Re: [O] is there a way to have =var_name= in table

[Bastien]

François Pinard  writes:

>Emphasis and monospace
>--
>
>You can make words *bold*, /italic/, _underlined_, `=code=' and
>`~verbatim~', and, if you must, `+strike-through+'.  Text in the code
>and verbatim string is not processed for Org mode specific syntax; it
>is exported verbatim.
>
> Is there any functional (or semantic?) difference between =code= and
> ~verbatim~?  

For the current LaTeX exporter, Yes.

> Could I use any to avoid escaping problems of the other?
> (A bit like ' versus " in some languages?)

  This is =co%de=.
  This is ~verb%atim~.

gets exported as

  This is \texttt{co\%de}.
  This is \verb~verb%atim~.

HTH,

-- 
 Bastien

Re: [O] README.org on github

[Bastien]

suvayu ali  writes:

>> Only sufficient demand for org-documents will foster betterment I guess.
>
> Yes I realise that. I have never interacted with GitHub staff for
> feature requests. Being a long time org-mode user (post-6.33, that's
> ages in org years :-p), maybe I should give that a try.

I will too -- I'm a shy user of github but I'm there and will try to
push for a better support if the need arises.

-- 
 Bastien

Re: [O] README.org on github

[Bastien]

Puneeth Chaganti  writes:

> I've tweeted to them at least a couple of times (in the past few
> months) regarding this, but haven't yet got any response from them.
> May be someone should send an email to supp...@github.com.  I got back
> replies for other things in about a week or so, on email.  In general,
> GitHub staff seem like a nice bunch of people to me.

Actually, I would love to see Org files supported on gitorious.org and
other free dVCS web services.  This would create a nice emulation among
them all.

-- 
 Bastien

Re: [O] Macros [was: Re: ATTR_HTML for a clickable image, howto?]

[Bastien]

Hi François,

François Pinard  writes:

> This (partly) replies to the message I sent a few minutes ago.  Before
> sending that message, I checked in the Org manual, and the manual is
> silent about the possibility of such escaping.
>
> The manual is also silent about nesting, which has been mentioned
> elsewhere in this thread.  The examples in the manual do not hint either
> about whether newlines are allowed or not in macro arguments.

Please contribute by sending patches or more readable hints on what
should be fixed... 

> If macros are there to stay in Org, it might be worth documenting a more
> complete specification about how to define and use them.

Macros are here to stay.  Please also remember the manual cannot cover
everything -- Worg can efficiently cover topics like this one.

Thanks for your help!

-- 
 Bastien

Re: [O] Presentation on Org-mode at Dunkerque (France)

[Bastien]

Hi Fabrice,

"Fabrice Niessen"
 writes:

> Just to tell you that I will make a presentation on Org-mode during the LaTeX
> day in Dunkerque (FR) on Wed 13th June 2012.

Great -- let's us know if the audience asks questions that are worth
asking here!

Good luck,

-- 
 Bastien

Re: [O] [Feature Request] org-mobile edit:add nodes

[Henning Weiss]

On Tue, May 22, 2012 at 7:54 PM, Bastien  wrote:

> Hi Henning,
>
> Henning Weiss  writes:
>
> > I have refined the edit nodes patch. Aaron Peromsik has helped me
> > with developing and testing it. He hasn't reported any problems with
> > it and I have been using it for a couple of weeks now without
> > experiencing any problems.
>
> Thanks.  Can someone else test this patch?  I'm not using org-mobile.el.


To make the testing of the new edit nodes more attractive, someone could
compile the new editnodes
branchfrom
mobileorg-android. This branch adds support for refiling, deleting and
archiving nodes. Further explanation can be found
here
.

Henning

Re: [O] stop comments and weblinks from being coloured and names of directories from being italised, /etc/

[Nick Dokos]

Bastien  wrote:

> Samuel Wales  writes:
> 
> > I think comments don't get exported, so it must be just regular Org?
> 
> Indeed.  Hence my guess.
> 
> Thanks Samuel!  We spend cents, you spread wisdom :)
> 

Hear, hear! One of these days I'll learn to read.

Nick

Re: [O] New exporter [was: Re: Using Org for a dissertation]

[François Pinard]

François Pinard  writes:

> Nicolas Goaziou  writes:

>> I'd rather pull you into writing a Texinfo back-end for the export
>> engine ;)

Well, Nicolas has been much helpful at getting me started on this one.

> I might aim Python.

Nicolas' works are so nicely done that it would be rather insane not
using them.  Even if Python is more fun and speedy to write than Emacs
Lisp, it has drawbacks in the context of Org.  I'll stick to Lisp.

François

P.S. I should quickly get a rotten implementation; it will then take
forever to get it back on track!  The usual story... :-)

Re: [O] is there a way to have =var_name= in table

[Michael Brand]

On Sat, Mar 31, 2012 at 9:24 PM, Stephen J. Barr  wrote:
[...]
> | =var1=    | this is the first var  |
[...]
> However, pressing [TAB] after writing =var1= causes #ERROR to show up.
[...]

Just for the records. This issue has been resolved in the meantime with:

commit 8342fdb70aa28edbb7b0b18bf1f3c0fd2dd561fa
Author: Bastien Guerry 
Date:   Tue May 1 02:03:12 2012 +0200

It was also on my list of someday/maybe...

Michael