Re: [O] org-publish bug

[Carsten Dominik]

On 31.5.2013, at 02:04, Marvin Doyley  wrote:

> Hi there,
> 
> I solved the problem. It turns out that I needed to include
> 
> #+index:

Hi Marvin,

does this need to be documented somewhere?  If so, can you propose a patch?

Cheers

- Carsten

> 
> cheers,
> M
> 

Re: [O] [RFC] Extend :float attribute to src blocks and normalize syntax

[Nicolas Goaziou]

Hello,

Carsten Dominik  writes:

> I like the possibilities this opens, in particular to set a nil value.
> We could be nice to users and interpret `table' and `figure' as t.
> This is not clean, but nice... :)

Do you mean, it should interpret only "table" (or "figure") as t, or
"anything-not-meaningful" too?


Regards,

-- 
Nicolas Goaziou

Re: [O] XeLaTeX and the new exporter

[Carsten Dominik]

Hi Christopher,

Would you like to provide a patch?

- Carsten

On 31.5.2013, at 09:58, Christopher Witte  wrote:

> Sorry for the late reply.
> 
> I'm not entirely sure either, I pretty much just blindly followed the 
> instructions on the FAQ.  I don't think this is at all the minimum you need 
> to get xelatex working, it also sets up a few other things.  For instance it 
> used latexmk instead of just recompiling a few times.  Perhaps the FAQ should 
> be split up into a few different questions:
> 1. minimum setup for XeLaTeX, something similar to your setup
> 2. how to use latexmk
> 
> Cheers,
> Chris
> 
> 
> 
> On 22 May 2013 19:07, Suvayu Ali  wrote:
> Hi Christopher,
> 
> On Tue, May 07, 2013 at 05:42:04PM +0200, Christopher Witte wrote:
> >
> > I had export working using XeLaTeX using the instructions from the
> > FAQ(with
> > some slight modifications), but after upgrading to the new export it
> > isn't working.  It appears the hook
> > org-export-latex-after-initial-vars-hook isn't defined anymore.
> >
> > Any advice on what I need to change to get it to work?
> 
> I have noticed discussions on this before and I fail to understand the
> need for all the setup mentioned in the above Worg entry.  I use XeLaTeX
> almost exclusively, and all I have is something like this:
> 
>   ;;; XeLaTeX customisations
>   ;; remove "inputenc" from default packages as it clashes with xelatex
>   (setf org-latex-default-packages-alist
> (remove '("AUTO" "inputenc" t) org-latex-default-packages-alist))
> 
>   (add-to-list 'org-latex-packages-alist '("" "xltxtra" t))
>   ;; choose Linux Libertine O as serif and Linux Biolinum O as sans-serif 
> fonts
>   (add-to-list 'org-latex-packages-alist '("" "libertineotf" t))
> 
>   ;; org to latex customisations, -shell-escape needed for minted
>   (setq org-export-dispatch-use-expert-ui t ; non-intrusive export dispatch
> org-latex-pdf-process   ; for regular export
> '("xelatex -shell-escape -interaction nonstopmode -output-directory 
> %o %f"
>   "xelatex -shell-escape -interaction nonstopmode -output-directory 
> %o %f"
>   "xelatex -shell-escape -interaction nonstopmode -output-directory 
> %o %f"))
> 
> For beamer export I add this line:
> 
>   #+LaTeX_HEADER: \setsansfont{Linux Biolinum O}
> 
> So far I have not encountered any problems.  Although I have to say, I
> do not use unicode in mathmode.
> 
> I am curious to know why others need all this elaborate setup to use
> XeLaTeX.
> 
> Cheers,
> 
> --
> Suvayu
> 
> Open source is the future. It sets us free.
> 
> 

Re: [O] How to join cells in tables and center content

[Carsten Dominik]

On 30.5.2013, at 20:53, Ivanov Dmitry  wrote:

> Suppose, I am writing a database table structure.
> Is it possible to join the 1-st two cells? And make 'table1' centered?
> Current view and desired:
> 
> 
> | table1 |   |  | table1 |
> |+---+  |+---+
> | id | value |->| id | value |
> ||   |  ||   |
> 
> 
> I understand, that it will require programming. Just give me a hint, where is 
> the function, expanding table cells, and I'll try to implement it.

Hi Dmitry,

you can create such tables using table.el and use them in Org.
But the org-mode tables will not accommodate such a feature,
would be too hard.

- Carsten

Re: [O] [html] non-lists showing up as lists

[Nicolas Goaziou]

Hello,


Alan L Tyree  writes:

> I have also been bedeviled by this problem. In a long manuscript it is
> all too common. Here is a real example of a footnote and its HTML
> export:
>
> ===
>
> [fn:79] Some commentators have questioned whether it is an
> 'exception'. The argument is that it is merely part of the bank's duty
> not to be part of any fraud of which it has knowledge. See Ricky J
> Lee, Strict compliance and the fraud exception: balancing the
> interests of mercantile traders in the modern law of documentary
> credits, (2008) Macquarie Journal of Business Law
> 137. There is merit to this argument, but few
> practical consequences.
>

[...]

By default, a number followed by a dot or a parenthesis at the beginning
of a line starts a plain list. There is nothing new here. Use M-RET
after "but few", and you'll see this is not related to export.

The filling mechanism should prevent this situation from happening. If
it's not the case, please provide an ECM, as I cannot find one.


Regards,

-- 
Nicolas Goaziou

Re: [O] [PATCH v2] org.el: Don't flyspell check within source code blocks

[Carsten Dominik]

On 1.6.2013, at 08:15, Carsten Dominik  wrote:

> Hi Trevor,
> 
> have you noticed an impact of this patch on normal typing performance?
> This is something we need to be extremely careful about.

Sorry, I see that Matt has already done some profiling.  OK, I have applied 
this patch - lets see how it behaves.

- Carsten

> 
> - Carsten
> 
> On 30.5.2013, at 02:49, Trevor Murphy  wrote:
> 
>> * lisp/org.el (org-mode-flyspell-verify): Add check for
>> `org-in-src-block-p'.
>> 
>> TINYCHANGE
>> ---
>> lisp/org.el | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>> 
>> diff --git a/lisp/org.el b/lisp/org.el
>> index 94078f9..77de2d7 100644
>> --- a/lisp/org.el
>> +++ b/lisp/org.el
>> @@ -23596,7 +23596,8 @@ To get rid of the restriction, use 
>> \\[org-agenda-remove-restriction-lock]."
>>   (not (member-ignore-case word (org-get-export-keywords)))
>>   (not (member-ignore-case
>> word (mapcar 'car org-element-block-name-alist)))
>> - (not (member-ignore-case word '("BEGIN" "END" "ATTR"))
>> + (not (member-ignore-case word '("BEGIN" "END" "ATTR")))
>> + (not (org-in-src-block-p)
>> 
>> (defun org-remove-flyspell-overlays-in (beg end)
>>  "Remove flyspell overlays in region."
>> -- 
>> 1.8.3
>> 
>> 
> 

Re: [O] [RFC] Extend :float attribute to src blocks and normalize syntax

[Carsten Dominik]

On 31.5.2013, at 17:37, Nicolas Goaziou  wrote:

> Hello,
> 
> The following patch extends :float attribute to src blocks (so they are
> on par with tables and images). It also slightly changes syntax for this
> attribute:
> 
>  || Old   | New  |
>  |+---+--|
>  | Tables | :float table  | :float t |
>  | Images | :float figure | :float t | 
> 
> With this patch :float attribute also accepts a nil value in all cases,
> preventing any floating mechanism, even if a caption is provided. In
> particular, it replaces :long-listing attribute for src blocks:
> 
>  || Old | New|
>  |+-+|
>  | Src blocks | :long-listing t | :float nil |
> 
> Overall, it makes :float syntax a bit more regular, but it implies some
> gotchas.

Hi Nicolas,

I like the possibilities this opens, in particular to set a nil value.
We could be nice to users and interpret `table' and `figure' as t.
This is not clean, but nice... :)

- Carsten

> 
> WDYT?
> 
> 
> Regards,
> 
> -- 
> Nicolas Goaziou
> From 0bf638246d91e5d855836ceeb24b405b3688729f Mon Sep 17 00:00:00 2001
> From: Nicolas Goaziou 
> Date: Mon, 20 May 2013 10:43:18 +0200
> Subject: [PATCH 1/2] ox-latex: Extend :float attribute to source blocks and
> normalize its values
> 
> * lisp/ox-latex.el (org-latex-src-block): Handle :float attribute. Its
>  value can be set to "t", "multicolumn" or "nil".  Also
>  remove :long-listing attribute, which is now replaced with :float
>  nil.
> (org-latex--org-table): Replace :float table with :float t.
> (org-latex--inline-image): Replace :float figure with :float t.
> (org-latex-long-listings): Remove variable.
> * doc/org.texi (@LaTeX{} specific attributes): Document new :float values.
> ---
> doc/org.texi |  37 +
> lisp/ox-latex.el | 162 ---
> 2 files changed, 110 insertions(+), 89 deletions(-)
> 
> diff --git a/doc/org.texi b/doc/org.texi
> index 290c671..408d00d 100644
> --- a/doc/org.texi
> +++ b/doc/org.texi
> @@ -11597,10 +11597,11 @@ environment, like @code{tabularx}, 
> @code{longtable}, @code{array},
> @code{tabu}, @code{bmatrix}@enddots{}  It defaults to
> @code{org-latex-default-table-environment} value.
> @item :float
> +@itemx :placement
> Float environment for the table.  Possible values are @code{sidewaystable},
> -@code{multicolumn} and @code{table}.  If unspecified, a table with a caption
> -will have a @code{table} environment.  Moreover, @code{:placement} attribute
> -can specify the positioning of the float.
> +@code{multicolumn}, @code{t} and @code{nil}.  When unspecified, a table with
> +a caption will have a @code{table} environment.  Moreover, @code{:placement}
> +attribute can specify the positioning of the float.
> @item :align
> @itemx :font
> @itemx :width
> @@ -11675,12 +11676,18 @@ without specifying caption by setting the 
> @code{:float} attribute.  You may
> also set it to:
> @itemize @minus
> @item
> -@code{wrap}: if you would like to let text flow around the image.  It will
> -make the figure occupy the left half of the page.
> +@code{t}: if you want to use the standard @samp{figure} environment.  It is
> +used by default if you provide a caption to the image.
> @item
> @code{multicolumn}: if you wish to include an image which spans multiple
> columns in a page.  This will export the image wrapped in a @code{figure*}
> environment.
> +@item
> +@code{wrap}: if you would like to let text flow around the image.  It will
> +make the figure occupy the left half of the page.
> +@item
> +@code{nil}: if you need to avoid any floating environment, even when
> +a caption is provided.
> @end itemize
> @noindent
> To modify the placement option of any floating environment, set the
> @@ -11711,13 +11718,23 @@ omitted).
> @subsubheading Source blocks in @LaTeX{} export
> @cindex source blocks, in @LaTeX{} export
> 
> -In addition to syntax defined in @ref{Literal examples}, names and
> -captions (@pxref{Images and tables}), source blocks also accept a
> -@code{:long-listing} attribute, which prevents the block from floating
> -when non-@code{nil}.
> +In addition to syntax defined in @ref{Literal examples}, names and captions
> +(@pxref{Images and tables}), source blocks also accept a @code{:float}
> +attribute.  You may set it to:
> +@itemize @minus
> +@item
> +@code{t}: if you want to make the source block a float.  It is the default
> +value when a caption is provided.
> +@item
> +@code{mulicolumn}: if you wish to include a source block which spans multiple
> +colums in a page.
> +@item
> +@code{nil}: if you need to avoid any floating evironment, even when a caption
> +is provided.  It is useful for source code that may not fit in a single page.
> +@end itemize
> 
> @example
> -#+ATTR_LATEX: :long-listing t
> +#+ATTR_LATEX: :float nil
> #+BEGIN_SRC emacs-lisp
> Code that may not fit in a single page.
> #+END_SRC
> diff --git a/lisp/ox-

Re: [O] [RFC] Extend :float attribute to src blocks and normalize syntax

[Nicolas Goaziou]

Hello,

Nick Dokos  writes:

> Is a binary value for :float enough? I thought (maybe incorrectly)
> that the value of :float would determine (at least for latex export)
> the floating environment for the table, giving one the option to use
> longtable or sidewaystable e.g. Is that the case? If so, how would you
> handle it in the new regime?

The value for :float is not binary. Tables accept :float multicolumn
and :float sidewaystable. Images accept :float wrap and :float
multicolumn. Src blocks will accept :float multicolumn.

I didn't mention it since I focused on the syntax changes. Though, the
patch comes with an org.texi update where these attributes are
described.


Regards,

-- 
Nicolas Goaziou

Re: [O] how i can unsubscribe this mail list ?

[Carsten Dominik]

Hi,

I cannot find you in the member list.  Under what email are you subscribed?

- Carsten

On 30.5.2013, at 14:50, Tongzhu Zhang  wrote:

> i want read this mail list from gnus in emacs, but i cant remember my 
> password, i have been already tried : 
> https://lists.gnu.org/mailman/options/emacs-orgmode
> 
> but no mail received .
> how i can do now ? 

Re: [O] default face org-column

[Carsten Dominik]

On 30.5.2013, at 04:43, Xiao-Yong Jin  wrote:

> Hi,
> 
> In org-faces.el,
> 
> (when (fboundp 'set-face-attribute)
>   ;; Make sure that a fixed-width face is used when we have a column table.
>   (set-face-attribute 'org-column nil
> :height (face-attribute 'default :height)
> :family (face-attribute 'default :family)))

Hi Xiao,

I remember that I struggled with the problem that I had to make sure that 
column view used a fixed-width face - and this was the solution that worked - 
not a particular pretty one, admittedly.

Do you have an idea on how to change this code that it will always work?  I'd 
be very happy to accept a good patch.

- Carsten

> 
> I understand why you did this, but it is not quite logical, and somewhat 
> invasive.  First, you certainly do not do this with org-table.  Then why 
> org-column specifically?  Second, it overwrites the the value I set in the 
> emacs theme or custom-set-faces.  Third, the end result is quite bizarre and 
> odd-looking.  The "default" height and "default" family is some how not what 
> I set for the frame, because the font family and size is set when emacs 
> starts up and loaded the org-mode.  When I use set-frame-font or 
> text-scale-adjust, org-column will stick with the old font family and size.  
> In fact, because the font family for org-column and org-column-title are 
> different, the result is just bad.
> 
> I don't think it is only my problem, but I'll describe my setup for 
> themes/font.  I use default-frame-alist to set the font family and size—The 
> above code will not pick up this setup.  I use load-theme and enable-theme to 
> load the theme I want.  Sometimes I use set-frame-font or text-scale-adjust 
> to get a pleasantly looking texts temporary.  I usually use fixed-width font, 
> so the above code is not doing any good.
> 
> For the time being, I commented out the above code.
> 
> Best,
> Xiao-Yong
> 

Re: [O] [PATCH v2] org.el: Don't flyspell check within source code blocks

[Carsten Dominik]

Hi Trevor,

have you noticed an impact of this patch on normal typing performance?
This is something we need to be extremely careful about.

- Carsten

On 30.5.2013, at 02:49, Trevor Murphy  wrote:

> * lisp/org.el (org-mode-flyspell-verify): Add check for
>  `org-in-src-block-p'.
> 
> TINYCHANGE
> ---
> lisp/org.el | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/lisp/org.el b/lisp/org.el
> index 94078f9..77de2d7 100644
> --- a/lisp/org.el
> +++ b/lisp/org.el
> @@ -23596,7 +23596,8 @@ To get rid of the restriction, use 
> \\[org-agenda-remove-restriction-lock]."
>(not (member-ignore-case word (org-get-export-keywords)))
>(not (member-ignore-case
>  word (mapcar 'car org-element-block-name-alist)))
> -  (not (member-ignore-case word '("BEGIN" "END" "ATTR"))
> +  (not (member-ignore-case word '("BEGIN" "END" "ATTR")))
> +  (not (org-in-src-block-p)
> 
> (defun org-remove-flyspell-overlays-in (beg end)
>   "Remove flyspell overlays in region."
> -- 
> 1.8.3
> 
> 

Re: [O] Expanded property drawers as per file option

[Carsten Dominik]

On 29.5.2013, at 22:09, Karl Voit  wrote:

> * Feng Shu  wrote:
>> Thorsten Jolitz  writes:
>> 
>>> Thorsten Jolitz  writes:
>>> 
>>> ,-
>>> | (defun find-org-contracts ()
>>> | (interactive)
>>> | (find-file "/path/to/contracts.org")
>>> | (show-all))
>>> | 
>>> | M-x find-org-contracts
>>> `-
>> 
>> I use:
>> #+STARTUP: showeverything
> 
> Those two methods result in expanded properties, yes.
> 
> However, I obviously was not precise enough to explain my
> requirement which is more complicated than "showeverything"
> 
> 
> I would like to have all headings folded when I open the file (as it
> is now). Then I navigate to a heading of a person by using text
> search or arrow keys and TAB (to expand hierarchies). 

Hi,

an imperfect solution that might work for you anyway is to create a local 
version
of `org-cycle-hook' and remove `org-cycle-hide-drawers' from the value of this
variable.  This is imperfect because org-cycle-hide-drawers is also called
sometimes explicitly, for example after moving a subtree.  But it will cause
drawers to stay open after TAB.

To try this, make the following line the first line of your file:

# -*- mode: org; org-cycle-hook: (org-cycle-hide-archived-subtrees 
org-cycle-hide-inline-tasks org-cycle-show-empty-lines 
org-optimize-window-after-visibility-change) -*-

Then kill the buffer and visit it again.  Check the value of `org-cycle-hook' 
with `C-h v', you should see that the variable has a local value in this buffer.

If you then press TAB twice on"Peter", the drawer will be open.

Hope this helps.

- Carsten


> 
> On the heading of the "target" person, I want TAB to expand also the
> properties drawer, not only the content of the heading with
> properties collapsed.
> 
> 
> Example:
> 
> I start with contacts.org like this:
> 
>* job
>* family
> 
> I go to "job" and expand using TAB:
> 
>* job
>  * Bob
>  * Peter
>  * Susan
>* family
> 
> After that, I navigate to "Peter" and press TAB once again to expand
> the heading of Peter *and* its property drawer all together (only
> for "Peter"):
> 
>* job
>  * Bob
>  * Peter
>:PROPERTIES:
>:EMAIL: pe...@example.com
>:COMPANY: Acme
>:ADDRESS: Hiscity, hisstreet 42
>:END:
> 
>- met him at conference XY in 2009
>- works in the field of foobar
> 
>  * Susan
>* family
> 
> 
> The desired difference to my current situation is, that I do not
> have to navigate on the PROPERTY line and press TAB to open the
> drawer for email, company name, address, and so forth.
> 
> 
> Usual behavior: PROPERTY drawer stays collapsed when its
> corresponding heading gets expanded.
> 
> My wish: PROPERTY drawer gets collapsed when its corresponding
> heading gets expanded.
> 
> 
> I know that this is a very specific requirement and it spares me
> only one positioning effort followed by TAB. However, for contacts
> it would eliminate one annoyance for my work flow :-)
> 
> Thanks for your comments, thoughts, tipps!
> 
> 
> -- 
> mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
>> get Memacs from https://github.com/novoid/Memacs <
> 
> https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github
> 
> 

Re: [O] Please regenerate the refile cache with `C-0 C-c C-w'

[Carsten Dominik]

Hi Samuel,

could you go back to a much older Org version, like release_7.9.4 and check if 
this is still happening?  It would be an indication if it has to do with Org, 
or with something external like magit.

- Carsten

On 28.5.2013, at 23:28, Samuel Wales  wrote:

> This might not be reproducible as all I can do is give general information.
> 
> I am getting "Please regenerate the refile cache with `C-0 C-c C-w'"
> quite a lot recently.  Git master.
> 
> I use the refile cache and I also do restricted refile to :refile: and
> I use a verify function.
> 
> I use magit.el.
> 
> I know a long time ago, somebody made a change to magit to update the
> mode line with vc information, and that caused reverting of the
> buffer.  That was reverted because it was slow and breaking things.  I
> hope that hasn't returned?
> 
> All I can really report is that I get that error frequently now.
> 
> Thanks.
> 
> Samuel
> 
> -- 
> The Kafka Pandemic: http://thekafkapandemic.blogspot.com
> 
> The disease DOES progress.  MANY people have died from it.  ANYBODY can get 
> it.
> 

Re: [O] [PATCH] org-table-convert-region (was Re: Bug in org-table-convert-region?)

[Carsten Dominik]

On 28.5.2013, at 13:47, Thorsten Jolitz  wrote:

> Thorsten Jolitz  writes:
> 
>> Yes, I can confirm this. So either (interactive "rP") isn't a valid
>> combination, then its a bug in the org command3, or it is a valid
>> combination and should work - then its a bug in Emacs 24?
> 
> Its a bug in 'org-table-convert-region'. 
> 
> "PATCH":
> 
> replace
> 
> ,---
> | (interactive "rP")
> `---
> 
> with
> 
> ,-
> | (interactive "r\nP")
> `-

I have made this Change.

- Carsten

> 
> (Thanks to Andreas Röhler for the tip)
> 
> -- 
> cheers,
> Thorsten
> 
> 

Re: [O] [PATCH][ox-latex.el] Allow AUTO argument to org-latex-guess-babel-language.

[Achim Gratz]

Rasmus writes:
> This patch allows ox-latex to make a guess on which  language to use
> if babel is a default package.  See the head of the patch.

What's the status of your copyright assignment?  You're neither listed
as a contributor nor as one of the people whose papers are in processing
(see http://orgmode.org/worg/org-contribute.html) although you've
mentioned that you might consider assigning copyright just recently.


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

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

Re: [O] Org-mode contacts to Android

[Feng Shu]

Feng Shu  writes:

> Karl Voit  writes:
>
>> * Feng Shu  wrote:
>>> Karl Voit  writes:
>>>
 In the future, I plan to add a workflow that gets contact
 information form Org-mode (my central point of information) to my
 phone and so forth.
>>>
>>> If you use android phone, you can write a  function
>>> "org-contacts-export-to-sqlite3" which can export org-contacts  to
>>> android contacts.db
>>
>> Yes, I am using Android on my phone.
>>
>> No, I am not able to write a sqlite3 export in ELISP because I don't
>> know ELISP (yet) :-(
>>
>> However, why should I? You mentioned your VCard export method in
>> another email here. This sounds reasonable to me. I guess, I have to
>> test this method on my Android as well some time.
>
> The reason:
> 1. speed: very slow when import vcf to android(>100 contacts)
> 2. automatic: If we export to db directly, we only need update db to
>android phone,and don't need to run Vcardio in the phone 
>
>
> Maybe we can do like this:
>
> org-contacts -> vcf file ---vcf to sqlite3 command--> db --> push to android!

I'm very interested in integrating org and android phone effectively, 
so I want to share the solutions with others who are using android phone and 
org-mode!

I changed my setting again for unstable WIFI connection!

Integrating android phone with org  has many details to resolve:
1. speed(import vcf, import org file to org-mobile and so on)
2. WIFI problem!
3. Battery (I think this should be pay more attention when we use WIFI, 
   I use android app: Better Wifi on/off)
4. maximum possible automation. 

This is my new solution:

1. I use botsync, pull all my agenda.org to my phone by  sshd in computer
2. Change the keybinding "g" in the agenda buffer, 

#+begin_src emacs-lisp
(org-defkey org-agenda-mode-map "g" (lambda () (interactive)
  (org-agenda-redo t)
  (org-contacts-export-as-vcard)
  (org-mobile-push)))
#+end_src



-- 

[O] [PATCH][ox-latex.el] Allow AUTO argument to org-latex-guess-babel-language.

[Rasmus]

This patch allows ox-latex to make a guess on which  language to use
if babel is a default package.  See the head of the patch.

Two notes on the funcion:

1.  As far as I remember, if more than one language is loaded the
order is not neutral one one should issue a \selectlanguage{LANG}.  

2. Perhaps it should look for babel /and/ pologlossya or whatever the
package the xelatex and perhaps lualatex uses.  Any thoughs?

–Rasmus

-- 
Together we'll stand, divided we'll fall
>From dde65056267bcb4c1bfe23c2e66f570739bb72c7 Mon Sep 17 00:00:00 2001
From: "rasmus" 
Date: Sat, 1 Jun 2013 00:20:18 +0200
Subject: [PATCH] Allow AUTO argument to org-latex-guess-babel-language.

	* ox-latex.el (org-latex-guess-babel-language): ignore AUTO
	if argument.
	* ox-latex.el (org-lat ex-guess-babel-language): use language
	if is not in =`org-latex-inputenc-alist'=.
	* ox-latex.el	 (org-latex-guess-babel-language): retain case
	in final regexp of function.

Behavior changes:
1.  =("AUTO" "babel" t)= works like ("AUTO" "inputenc" t) in
	=`org-latex-default-packages-alist'=. I.e. the default
	language is choosen.
2. if #+LANGUAGE: mylang then then \usepackage[mylang]{babel} in
	outpu.

TINYCHANGE
---
 lisp/ox-latex.el | 12 +++-
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/lisp/ox-latex.el b/lisp/ox-latex.el
index 3a01693..033d318 100644
--- a/lisp/ox-latex.el
+++ b/lisp/ox-latex.el
@@ -929,19 +929,21 @@ Return the new header."
 ;; If no language is set or Babel package is not loaded, return
 ;; HEADER as-is.
 (if (or (not (stringp language-code))
-	(not (string-match "usepackage\\[\\(.*\\)\\]{babel}" header)))
+	(not (string-match "usepackage\\[\\(AUTO\\)?,?\\(.*\\)\\]{babel}" header)))
 	header
   (let ((options (save-match-data
-		   (org-split-string (match-string 1 header) ",")))
-	(language (cdr (assoc language-code
-  org-latex-babel-language-alist
+		   (org-split-string (match-string 2 header) ",")))
+	(language (or
+		   (cdr (assoc language-code
+  org-latex-babel-language-alist))
+		   language-code)))
 	;; If LANGUAGE is already loaded, return header.  Otherwise,
 	;; append LANGUAGE to other options.
 	(if (member language options) header
 	  (replace-match (mapconcat 'identity
 (append options (list language))
 ",")
-			 nil nil header 1))
+			 t nil header 1))

 (defun org-latex--find-verb-separator (s)
   "Return a character not used in string S.
--
1.8.3

Re: [O] Org-mode contacts to Android

[Feng Shu]

Karl Voit  writes:

> * Feng Shu  wrote:
>> Karl Voit  writes:
>>
>>> In the future, I plan to add a workflow that gets contact
>>> information form Org-mode (my central point of information) to my
>>> phone and so forth.
>>
>> If you use android phone, you can write a  function
>> "org-contacts-export-to-sqlite3" which can export org-contacts  to
>> android contacts.db
>
> Yes, I am using Android on my phone.
>
> No, I am not able to write a sqlite3 export in ELISP because I don't
> know ELISP (yet) :-(
>
> However, why should I? You mentioned your VCard export method in
> another email here. This sounds reasonable to me. I guess, I have to
> test this method on my Android as well some time.

The reason:
1. speed: very slow when import vcf to android(>100 contacts)
2. automatic: If we export to db directly, we only need update db to
   android phone,and don't need to run Vcardio in the phone 


Maybe we can do like this:

org-contacts -> vcf file ---vcf to sqlite3 command--> db --> push to android!


-- 

[O] Org-mode contacts to Android (was: Handling outdated contact information)

[Karl Voit]

* Feng Shu  wrote:
> Karl Voit  writes:
>
>> In the future, I plan to add a workflow that gets contact
>> information form Org-mode (my central point of information) to my
>> phone and so forth.
>
> If you use android phone, you can write a  function
> "org-contacts-export-to-sqlite3" which can export org-contacts  to
> android contacts.db

Yes, I am using Android on my phone.

No, I am not able to write a sqlite3 export in ELISP because I don't
know ELISP (yet) :-(

However, why should I? You mentioned your VCard export method in
another email here. This sounds reasonable to me. I guess, I have to
test this method on my Android as well some time.

-- 
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
   > get Memacs from https://github.com/novoid/Memacs <

https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github

Re: [O] [RFC] Extend :float attribute to src blocks and normalize syntax

[Nick Dokos]

Nicolas Goaziou  writes:


> The following patch extends :float attribute to src blocks (so they are
> on par with tables and images). It also slightly changes syntax for this
> attribute:
>
>   || Old   | New  |
>   |+---+--|
>   | Tables | :float table  | :float t |
>   | Images | :float figure | :float t | 
>
> With this patch :float attribute also accepts a nil value in all cases,
> preventing any floating mechanism, even if a caption is provided. In
> particular, it replaces :long-listing attribute for src blocks:
>
>   || Old | New|
>   |+-+|
>   | Src blocks | :long-listing t | :float nil |
>
> Overall, it makes :float syntax a bit more regular, but it implies some
> gotchas.
>
> WDYT?
>

Is a binary value for :float enough? I thought (maybe incorrectly)
that the value of :float would determine (at least for latex export)
the floating environment for the table, giving one the option to use
longtable or sidewaystable e.g. Is that the case? If so, how would you
handle it in the new regime?

--
Nick

Re: [O] [html] non-lists showing up as lists

[Alan L Tyree]

On 01/06/13 03:01, Nicolas Goaziou wrote:

Hello,


Samuel Wales  writes:


The 30 and the - get exported as lists.


As they should.


===
paragraph.  Emily died at age
30.  New sentence.

paragraph
- the list is long.
===

Filling


If filling creates this, then this is a bug. Could you provide an ECM
for this?




I have also been bedeviled by this problem. In a long manuscript it is 
all too common. Here is a real example of a footnote and its HTML export:


===

[fn:79] Some commentators have questioned whether it is an
'exception'. The argument is that it is merely part of the bank's duty
not to be part of any fraud of which it has knowledge. See Ricky J
Lee, Strict compliance and the fraud exception: balancing the
interests of mercantile traders in the modern law of documentary
credits, (2008) Macquarie Journal of Business Law
137. There is merit to this argument, but few
practical consequences.

===


Exported as:

=
79

Some commentators have questioned whether it is an 'exception'. The 
argument is that it is merely part of the bank's duty not to be part of 
any fraud of which it has knowledge. See Ricky J Lee, Strict compliance 
and the fraud exception: balancing the interests of mercantile traders 
in the modern law of documentary credits, (2008) Macquarie Journal of 
Business Law


   1. There is merit to this argument, but few

practical consequences.

=

Or this -- not a footnote, but in the main text:


The ICC has issued the International Standard Banking Practice
for the Examination of Documents under Documentary Credits (ISBP
2007) which attempts to clarify some of the issues.

=

Exported as:

===
 The ICC has issued the International Standard Banking Practice for the 
Examination of Documents under Documentary Credits (ISBP


   1. which attempts to clarify some of the issues.

==



Cheers,
Alan



--
Alan L Tyreehttp://www2.austlii.edu.au/~alan
Tel:  04 2748 6206  sip:172...@iptel.org

Re: [O] [RFC] Extend :float attribute to src blocks and normalize syntax

[Nicolas Goaziou]

Hello,

"Sebastien Vauban" 
writes:

> Does it have impact on centering as well? You speak of caption, and I remember
> that (at least, before), in LaTeX, when giving a caption to a figure, it was
> centered, otherwise not. Is there such interaction?

This patch is unrelated to centering.

Giving a caption to a table (or an image, or a src block) is equivalent
to ":float t", unless ":float nil" is already specified, in which case
caption is ignored.


Regards,

-- 
Nicolas Goaziou

Re: [O] installation

[Marcin Borkowski]

Dnia 2013-05-31, o godz. 08:04:37
Bastien  napisał(a):

> Hi Jacob,
> 
> I think your best starting point is here:
> 
>   http://emacsformacosx.com
> 
> Org-mode is part of Emacs, so Emacs is all what you need.
> 
> Then learn to use Emacs by reading the tutorial.
> 
> Then start editing an .org file -- and you're done!
> 
> (Well, nearly done.)

Also, after doing a tutorial, you might want to install Org-mode v8.0
(especially if you want to use the exporter).  There are some answers
on this list on how to do it easily.

And remember: Org-mode will *never* impose its complex features on
you.  Instead, it will make *you* impose more complex features on
yourself.

Mwahahahahahaha!

(BTW: I'm on my way on converting a friend to Org-mode - I converted
him to Emacs already;).)

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University

Re: [O] How to join cells in tables and center content

[Marcin Borkowski]

Dnia 2013-05-31, o godz. 08:06:58
Bastien  napisał(a):

> Hi Ivanov,
> 
> Ivanov Dmitry  writes:
> 
> > Suppose, I am writing a database table structure.
> > Is it possible to join the 1-st two cells? And make 'table1'
> > centered?
> 
> No.
> 
> > Current view and desired:
> >
> >
> > | table1 |   |  | table1 |
> > |+---+  |+---+
> > | id | value |->| id | value |
> > ||   |  ||   |
> >
> >
> > I understand, that it will require programming. Just give me a hint,
> > where is the function, expanding table cells, and I'll try to
> > implement it.
> 
> Most code is in org-table.el -- but beware that even with some
> programming skills this is a hard-perhaps-impossible task...

Just random thoughts here:

It would definitely require some syntax so that Org knows that you
don't want to just extend the whole column to the width of two
columns.  Maybe something like  (setting of the width), but
probably something along the lines of #+TBLFM (some kind of
syntax /below/ the table) might be better.

In general, joining cells seems to be a potentially tough problem,
especially if you want to allow joining them vertically, too
(and /years/ of LaTeX experience (not mine) show that if you give
people horizontal joining, at some point they /will/ want vertical
one...  In Polish, we have a saying for that: "give it a finger, and it
will bite off your hand";).)

That said, I'd welcome such a feature.

> Good luck,

Best,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University

Re: [O] Xemacs 21.5.32 and org-8.03, compilation problems

[Achim Gratz]

Uwe Brauer writes:
> You are right, this is a sad fact but true. The only person who cared,
> and knows enough Lisp is Michael Sperber, who right now is very busy.
>
> Actually I am right now very busy my self, but maybe in the next days I
> give it another try, now that you sent me this information!

I'll mention again that it would be really helpful to get ert running on
XEmacs.  I've managed to get it to the point where it loads, but then
infloops off its stack, presumably due to the heavy use of macros in
ert.


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

SD adaptation for Waldorf Blofeld V1.15B11:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

Re: [O] [RFC] Extend :float attribute to src blocks and normalize syntax

[Sebastien Vauban]

Hi Nicolas,

Nicolas Goaziou wrote:
> The following patch extends :float attribute to src blocks (so they are
> on par with tables and images). It also slightly changes syntax for this
> attribute:
>
>   || Old   | New  |
>   |+---+--|
>   | Tables | :float table  | :float t |
>   | Images | :float figure | :float t | 
>
> With this patch :float attribute also accepts a nil value in all cases,
> preventing any floating mechanism, even if a caption is provided. In
> particular, it replaces :long-listing attribute for src blocks:
>
>   || Old | New|
>   |+-+|
>   | Src blocks | :long-listing t | :float nil |
>
> Overall, it makes :float syntax a bit more regular, but it implies some
> gotchas.
>
> WDYT?

That it certainly is a great change -- I say that without testing it, but it
clearly is something I would call for.

Does it have impact on centering as well? You speak of caption, and I remember
that (at least, before), in LaTeX, when giving a caption to a figure, it was
centered, otherwise not. Is there such interaction?

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] mydisk.com down?

[Guido Van Hoecke]

Guido Van Hoecke  writes:

> Hi,
>
> Could it be that mydisk.com is down?

Can't sync my mobileorg data :(

> Anybody knows something more about this?

Or about other free WebDAV servers?
(My Dropbox account is not an option)

>
> TIA,
>
>
> Guido
>
> --
> You can't play your friends like marks, kid.
>   -- Henry Gondorf, "The Sting"

[O] mydisk.com down?

[Guido Van Hoecke]

Hi,

Could it be that mydisk.com is down?

Anybody knows something more about this?

TIA,


Guido

--
You can't play your friends like marks, kid.
-- Henry Gondorf, "The Sting"

Re: [O] [html] non-lists showing up as lists

[Nicolas Goaziou]

Hello,


Samuel Wales  writes:

> The 30 and the - get exported as lists.

As they should.

> ===
> paragraph.  Emily died at age
> 30.  New sentence.
>
> paragraph
> - the list is long.
> ===
>
> Filling 

If filling creates this, then this is a bug. Could you provide an ECM
for this?

> and yanking can create lines like those.

On the other hand, I think it's the user's responsibility to check what
he is yanking. Anyway, there's no way to tell if he wants to yank a real
list or not.

> If so, is there a way to change it so that it requires a blank line
> before every list?

No: Org lists can start at column 0.


Regards,

-- 
Nicolas Goaziou

[O] [html] non-lists showing up as lists

[Samuel Wales]

The 30 and the - get exported as lists.

===
paragraph.  Emily died at age
30.  New sentence.

paragraph
- the list is long.
===

Filling and yanking can create lines like those.

Perhaps this is intended behavior?  If so, is there a way to change it
so that it requires a blank line before every list?

Thanks.

Samuel

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

The disease DOES progress.  MANY people have died from it.  ANYBODY can get it.

[O] org-checklist warning/elpa related?

[Robert Horn]

I'm getting warnings about org-checklist that don't seem to be related
to any real problem.  I've noticed no functional problems with
org-checklist.

This is with org elpa 20130522.  I get the following warnings in
*Messages* when I change emacs color themes.

Auto-saving...done   <--- harmless automatic save
Invalid face reference: nil [4 times]  <--- from themes with glitches
Problems while trying to load feature `org-checklist'
Auto-saving...  <--- automatic save, with no face warning from good themes
Problems while trying to load feature `org-checklist'

I'm not sure what is causing the "Problems while trying to load feature
'org-checklist'".  

Whatever it is does not seem to have any affect on proper behavior of
checklists in org, so I suspect some packaging or elpa related issue.

R Horn

[O] [RFC] Extend :float attribute to src blocks and normalize syntax

[Nicolas Goaziou]

Hello,

The following patch extends :float attribute to src blocks (so they are
on par with tables and images). It also slightly changes syntax for this
attribute:

  || Old   | New  |
  |+---+--|
  | Tables | :float table  | :float t |
  | Images | :float figure | :float t | 

With this patch :float attribute also accepts a nil value in all cases,
preventing any floating mechanism, even if a caption is provided. In
particular, it replaces :long-listing attribute for src blocks:

  || Old | New|
  |+-+|
  | Src blocks | :long-listing t | :float nil |

Overall, it makes :float syntax a bit more regular, but it implies some
gotchas.

WDYT?


Regards,

-- 
Nicolas Goaziou
>From 0bf638246d91e5d855836ceeb24b405b3688729f Mon Sep 17 00:00:00 2001
From: Nicolas Goaziou 
Date: Mon, 20 May 2013 10:43:18 +0200
Subject: [PATCH 1/2] ox-latex: Extend :float attribute to source blocks and
 normalize its values

* lisp/ox-latex.el (org-latex-src-block): Handle :float attribute. Its
  value can be set to "t", "multicolumn" or "nil".  Also
  remove :long-listing attribute, which is now replaced with :float
  nil.
(org-latex--org-table): Replace :float table with :float t.
(org-latex--inline-image): Replace :float figure with :float t.
(org-latex-long-listings): Remove variable.
* doc/org.texi (@LaTeX{} specific attributes): Document new :float values.
---
 doc/org.texi |  37 +
 lisp/ox-latex.el | 162 ---
 2 files changed, 110 insertions(+), 89 deletions(-)

diff --git a/doc/org.texi b/doc/org.texi
index 290c671..408d00d 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -11597,10 +11597,11 @@ environment, like @code{tabularx}, @code{longtable}, @code{array},
 @code{tabu}, @code{bmatrix}@enddots{}  It defaults to
 @code{org-latex-default-table-environment} value.
 @item :float
+@itemx :placement
 Float environment for the table.  Possible values are @code{sidewaystable},
-@code{multicolumn} and @code{table}.  If unspecified, a table with a caption
-will have a @code{table} environment.  Moreover, @code{:placement} attribute
-can specify the positioning of the float.
+@code{multicolumn}, @code{t} and @code{nil}.  When unspecified, a table with
+a caption will have a @code{table} environment.  Moreover, @code{:placement}
+attribute can specify the positioning of the float.
 @item :align
 @itemx :font
 @itemx :width
@@ -11675,12 +11676,18 @@ without specifying caption by setting the @code{:float} attribute.  You may
 also set it to:
 @itemize @minus
 @item
-@code{wrap}: if you would like to let text flow around the image.  It will
-make the figure occupy the left half of the page.
+@code{t}: if you want to use the standard @samp{figure} environment.  It is
+used by default if you provide a caption to the image.
 @item
 @code{multicolumn}: if you wish to include an image which spans multiple
 columns in a page.  This will export the image wrapped in a @code{figure*}
 environment.
+@item
+@code{wrap}: if you would like to let text flow around the image.  It will
+make the figure occupy the left half of the page.
+@item
+@code{nil}: if you need to avoid any floating environment, even when
+a caption is provided.
 @end itemize
 @noindent
 To modify the placement option of any floating environment, set the
@@ -11711,13 +11718,23 @@ omitted).
 @subsubheading Source blocks in @LaTeX{} export
 @cindex source blocks, in @LaTeX{} export
 
-In addition to syntax defined in @ref{Literal examples}, names and
-captions (@pxref{Images and tables}), source blocks also accept a
-@code{:long-listing} attribute, which prevents the block from floating
-when non-@code{nil}.
+In addition to syntax defined in @ref{Literal examples}, names and captions
+(@pxref{Images and tables}), source blocks also accept a @code{:float}
+attribute.  You may set it to:
+@itemize @minus
+@item
+@code{t}: if you want to make the source block a float.  It is the default
+value when a caption is provided.
+@item
+@code{mulicolumn}: if you wish to include a source block which spans multiple
+colums in a page.
+@item
+@code{nil}: if you need to avoid any floating evironment, even when a caption
+is provided.  It is useful for source code that may not fit in a single page.
+@end itemize
 
 @example
-#+ATTR_LATEX: :long-listing t
+#+ATTR_LATEX: :float nil
 #+BEGIN_SRC emacs-lisp
 Code that may not fit in a single page.
 #+END_SRC
diff --git a/lisp/ox-latex.el b/lisp/ox-latex.el
index 3a01693..237378d 100644
--- a/lisp/ox-latex.el
+++ b/lisp/ox-latex.el
@@ -738,20 +738,6 @@ options will be applied to blocks of all languages."
 	   (string :tag "Minted option name ")
 	   (string :tag "Minted option value"
 
-(defcustom org-latex-long-listings nil
-  "When non-nil no listing will be wrapped within a float.
-
-Removing floats may break some functionalities.  For example, it
-will be impossib

Re: [O] Minor bug in org export to latex

[Rasmus]

It's not a bug.

> I find that a mathmode environment, bounded by $..$, that breaks across
> line boundaries, is not typeset correctly.

It just happens to work most of the times.  Use \(.\) when in doubt.


> I am attaching a minimal example org-file.
> When I type a lot of text in front of the mathmode so that the mathmode breaks
> across a line boundary, I find that it is not typeset properly as here: $(1 
> - \nu)$

but

 $(1
x -\nu)$

would work.  -/+ is being picked up because it starts a list.

Hope this helps,
Rasmus

-- 
⠠⠵

[O] Minor bug in org export to latex

[Robert Goldman]

I find that a mathmode environment, bounded by $..$, that breaks across
line boundaries, is not typeset correctly.

I am attaching a minimal example org-file.

Best,
r
#+TITLE: Latex Export bug on line boundaries
#+AUTHOR: Robert P. Goldman
#+DATE: <2013-05-31 Fri>
#+EMAIL: rpgold...@sift.info
#+OPTIONS: ':nil *:t -:t ::t <:t H:3 \n:nil ^:t arch:headline author:t c:nil
#+OPTIONS: creator:comment d:(not LOGBOOK) date:t e:t email:nil f:t inline:t
#+OPTIONS: num:t p:nil pri:nil stat:t tags:t tasks:t tex:t timestamp:t toc:t
#+OPTIONS: todo:t |:t
#+CREATOR: Emacs 24.3.50.3 (Org mode 8.0.3)
#+DESCRIPTION:
#+EXCLUDE_TAGS: noexport
#+KEYWORDS:
#+LANGUAGE: en
#+SELECT_TAGS: export

* Here is a good example

$(1 - \nu)$

* Here is a bad example

When I type a lot of text in front of the mathmode so that the mathmode breaks
across a line boundary, I find that it is not typeset properly as here: $(1 
- \nu)$

Re: [O] {New exporter] What happened to the export template

[Robert Goldman]

A very late follow-up:

I note that the Worg instructions for HTML export still cite 
org-insert-export-options-template: 

http://orgmode.org/worg/org-tutorials/org-publish-html-tutorial.html

Re: [O] [Patch] phone links...

[Michael Strey]

Daimrod  writes:

> While merging a patch (from Feng Shu) I have found a bug in
> `org-contacts-split-property'. Though the docstring says that OMIT-NULLS
> is forced to t when SEPARATORS is nil (just like `split-string'), it
> wasn't the case. I've pushed a fix; could you check on your side that it
> doesn't break anything in your workflow?

I'm fine with your update.  Thank you for the correction!

-- 
Michael Strey
mailto:mst...@strey.biz
http://www.strey.biz

Re: [O] refine org-babel-tangle-jump-to-org?

[Eric Schulte]

rai...@krugs.de (Rainer M. Krug) writes:

> Eric Schulte  writes:
>
>> rai...@krugs.de (Rainer M. Krug) writes:
>>
>>> Hi
>>>
>>> I am using  org-babel-tangle-jump-to-org when debugging code written in
>>> org and tangled. I have some longisch code blocks and it is always
>>> irritating, as it only jumps to the codde block. Would it be possible to
>>> extend the function, that it jumps to the line of the code?
>>> That would make this funktion much more user friendly.
>>>
>>
>> I've just pushed up a change which should make this change.  I tested
>> this against the example.C file tangled from the attached Org-mode file.
>
> Thanks - works much better now.
> Very nice - it jumps even to the location in an indirect buffer -
> perfect.
>
> Without trying to be a perfectionist, it is in most cases between one
> and three lines off.
>
> Is this only in y case? If yes, please let me know and I can send you an
> org file privately.
>

Please do send me a minimal example.  In my simple tests it was landing
on the same character as in the source code file.

>
> It would be really nice, if it would be possible to put the cursor on
> the same line, preferably same character? But it is definitely usable
> like this for debugging.
>
>>
>> * example
>>   :PROPERTIES:
>>   :tangle:   yes
>>   :comments: link
>>   :END:
>>
>> The required headers.
>> #+name: header
>> #+begin_src C
>>   #include 
>> #+end_src
>>
>> Here is the auxiliary function.
>> #+name: auxiliary
>> #+begin_src C
>>   void aux(char* arg){
>> printf("first argument: %s\n", arg);
>>   }
>> #+end_src
>>
>> Here is the main function.
>> #+name: main
>> #+begin_src C
>>   int main(int argc, char *argv[])
>>   {
>> aux(argv[1]);
>> return 0;
>>   }
>> #+end_src
>>
>>
>> While implementing this change I did notice that this jumping
>> functionality only appears to work with linked code blocks, 
>
> linked code blocks? Do you mean the header argument :comments link or,
> as I use :comments yes? If I remember correctly, when you announced this
> function, you explicitly mentioned that :comments yes is required for it
> to work?
>

I meant to type "named code blocks", but yes you want to use ":comments
link", as I use in that example.  See the manual page for the comments
header argument for more details.

Cheers,

>
>
> Thanks a lot,
>
> Rainer
>
>>which should
>> I believe is a bug.
>>
>> Best,
>>
>>>
>>> Thanks,
>>>
>>> Rainer

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

Re: [O] Handling outdated contact information

[Feng Shu]

Karl Voit  writes:

> * Daimrod  wrote:
>>
>> Hi Karl,
>
> Hi Daimrod!
>
>>> This is a very good patch, fixing an issue I also do have currently.
>>
>> I am curious, what was the issue?
>
> Sure: I do use contacts.org by myself and I tend to collect data
> about people and never delete any. For example, previously used
> phone numbers are quite handy in order to get a connection between
> old text messages or phone call logs and a person.
>
> However, I do not want to mess up current phone numbers with old
> ones.
>
> With this ignore feature, I am able to address this issue (in the
> future). For now, I do not export contact information from Org-mode
> to somewhere else (except: lbdb -> mutt). In the future, I plan to
> add a workflow that gets contact information form Org-mode (my
> central point of information) to my phone and so forth.

If you use android phone, you can write a  function
"org-contacts-export-to-sqlite3" which can export org-contacts  to android 
contacts.db

-- 

Re: [O] Status fix for "Regression in fill-paragraph behavior"?

[Nicolas Goaziou]

Hello,

"Wagemans, Peter"  writes:

> Nicolas Goaziou wrote:
>
>> Also, you have to admit that Org is a bit more complex than Text mode
>> (or Fundamental mode), and may have different requirements.
>
> It sure is a great tool, with a lot of useful functionality. But the
> new paragraph fill breaks my old workflows, so I am trying to find a
> way around that (preferably the easiest ;-). Is there some way or
> setting to tell org that in a node or perhaps all nodes in a subtree
> it should apply the adaptive fill from fill.el to text paragraphs, so
> that the fill-prefix is automatically recognized like in fundamental
> and text mode? Or is there some function that I can call (and bind to
> some key combination) to apply the old paragraph fill to some text
> paragraph?  So that plain text paragraphs and citations that don't use
> any org features can be filled in the old way.

You probably can bind the following function:

  (defun my-good-ole-filling-fun ()
(interactive)
(let ((fill-paragraph-function nil) (adaptive-fill-function nil))
  (fill-paragraph)))


Regards,

-- 
Nicolas Goaziou

Re: [O] Exporting output and graphics from R

[Sebastien Vauban]

SabreWolfy,

SabreWolfy wrote:
> Sebastien Vauban  writes:
>> AFAICT, you can't have both at the same time. Do you have a real
>> use case for this?
>
> Maybe I'm not using the right tool for the job. I thought it would be useful
> to be able to intersperse explanatory text with output:
>
> All crows are black. We know this from looking at crows. I analyzed a
> dataset using this code, and produced a graph as follows:
>
> #+BEGIN_SRC R :results graphics :file testout.png :exports both
> # load data, analyze, make graph
> #+END_SRC
>
> The above analysis shows that all crows are black. A table of observed
> results is as follows:
>
> #+BEGIN_SRC R :results
> # more R code using the same dataset
> # will only work if the dataset is loaded again
> #+END_SRC
  ^^^
because you don't use the ":session" header argument. Look at it.

> This can be summarized with the following results:
> #+BEGIN_SRC R :results graphics :file testout.png :exports both
> # R code plotting another graph and showing another output table
> #+END_SRC

Use ":noweb yes" and references to named code blocks.

> My idea is that I would like the R code included for my reference when
> reading the document. I would also like the explanatory text, etc. included,
> as well as the output and results for the people who will be reading the
> document.

Of course, that's the whole point of using Org + Babel. Thanks Eric and Dan,
once again...

> Easier just to do it all in LaTeX directly? But then the code is not live,
> like it is in Org.

N/A

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] Exporting output and graphics from R

[SabreWolfy]

Feng Shu  gmail.com> writes:

>  #+BEGIN_SRC R :results output :exports both
>  pngname <- "testout.png"
>  png(pngname)
>  plot(1:10, 1:10)
>  dev.off()
>  x <- 1:10
>  paste("[[./", pngname, "]]",sep="")
>  #+END_SRC

Thanks. This is a great suggestion.

Re: [O] Exporting output and graphics from R

[SabreWolfy]

Sebastien Vauban  writes:

> AFAICT, you can't have both at the same time. Do you have a real
> use case for this?

Maybe I'm not using the right tool for the job. I thought it would be useful
to be able to intersperse explanatory text with output:

--8<---cut here---start->8---
All crows are black. We know this from looking at crows. I analyzed a
dataset using this code, and produced a graph as follows:

#+BEGIN_SRC R :results graphics :file testout.png :exports both
# load data, analyze, make graph
#+END_SRC

The above analysis shows that all crows are black. A table of observed
results is as follows:

#+BEGIN_SRC R :results
# more R code using the same dataset
# will only work if the dataset is loaded again
#+END_SRC

This can be summarized with the following results:
#+BEGIN_SRC R :results graphics :file testout.png :exports both
# R code plotting another graph and showing another output table
#+END_SRC
--8<---cut here---end--->8---

My idea is that I would like the R code included for my reference when
reading the document. I would also like the explanatory text, etc. included,
as well as the output and results for the people who will be reading the
document.

Easier just to do it all in LaTeX directly? But then the code is not live,
like it is in Org.

Re: [O] Handling outdated contact information

[Feng Shu]

Daimrod  writes:

> Karl Voit  writes:
>
>> * Daimrod  wrote:
>>>
>>> Hi Karl,
>>
>> Hi Daimrod!
>>
 This is a very good patch, fixing an issue I also do have currently.
>>>
>>> I am curious, what was the issue?
>>
>> Sure: I do use contacts.org by myself and I tend to collect data
>> about people and never delete any. For example, previously used
>> phone numbers are quite handy in order to get a connection between
>> old text messages or phone call logs and a person.
>>
>> However, I do not want to mess up current phone numbers with old
>> ones.
>>
>> With this ignore feature, I am able to address this issue (in the
>> future). For now, I do not export contact information from Org-mode
>> to somewhere else (except: lbdb -> mutt). In the future, I plan to
>> add a workflow that gets contact information form Org-mode (my
>> central point of information) to my phone and so forth.
>

I use SSHdroid in my android phone, and use keybinding  F12 to  pull vcf
file to my phone.  In my phone, I use VcardIO update my contacts


#+begin_src emacs-lisp
(global-set-key (kbd "") '(lambda () (interactive) 
(progn (org-mobile-push)
  
(org-contacts-export-as-vcard)
  (shell-command
  "scp
  
~/Documents/org-mobile/*
  
root@192.168.1.234:/sdcard/org-mobile/")
#+end_src emacs-lisp

> I see, thanks for the explanation.

-- 

Re: [O] Handling outdated contact information

[Daimrod]

Karl Voit  writes:

> * Daimrod  wrote:
>>
>> Hi Karl,
>
> Hi Daimrod!
>
>>> This is a very good patch, fixing an issue I also do have currently.
>>
>> I am curious, what was the issue?
>
> Sure: I do use contacts.org by myself and I tend to collect data
> about people and never delete any. For example, previously used
> phone numbers are quite handy in order to get a connection between
> old text messages or phone call logs and a person.
>
> However, I do not want to mess up current phone numbers with old
> ones.
>
> With this ignore feature, I am able to address this issue (in the
> future). For now, I do not export contact information from Org-mode
> to somewhere else (except: lbdb -> mutt). In the future, I plan to
> add a workflow that gets contact information form Org-mode (my
> central point of information) to my phone and so forth.

I see, thanks for the explanation.

-- 
Daimrod/Greg


signature.asc
Description: PGP signature

[O] Handling outdated contact information (was: [PATCH] org-contacts.el: add expire feature)

[Karl Voit]

* Daimrod  wrote:
>
> Hi Karl,

Hi Daimrod!

>> This is a very good patch, fixing an issue I also do have currently.
>
> I am curious, what was the issue?

Sure: I do use contacts.org by myself and I tend to collect data
about people and never delete any. For example, previously used
phone numbers are quite handy in order to get a connection between
old text messages or phone call logs and a person.

However, I do not want to mess up current phone numbers with old
ones.

With this ignore feature, I am able to address this issue (in the
future). For now, I do not export contact information from Org-mode
to somewhere else (except: lbdb -> mutt). In the future, I plan to
add a workflow that gets contact information form Org-mode (my
central point of information) to my phone and so forth.

-- 
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
   > get Memacs from https://github.com/novoid/Memacs <

https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github

Re: [O] [PATCH] org-contacts.el: add expire feature

[Karl Voit]

* Feng Shu  wrote:
>
> I have changed it to "IGNORE"

Thank you very much!

It will help your users to learn and understand this cool feature!

-- 
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
   > get Memacs from https://github.com/novoid/Memacs <

https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github

Re: [O] XeLaTeX and the new exporter

[Christopher Witte]

Sorry for the late reply.

I'm not entirely sure either, I pretty much just blindly followed the
instructions on the FAQ.  I don't think this is at all the minimum you need
to get xelatex working, it also sets up a few other things.  For instance
it used latexmk instead of just recompiling a few times.  Perhaps the FAQ
should be split up into a few different questions:
1. minimum setup for XeLaTeX, something similar to your setup
2. how to use latexmk

Cheers,
Chris



On 22 May 2013 19:07, Suvayu Ali  wrote:

> Hi Christopher,
>
> On Tue, May 07, 2013 at 05:42:04PM +0200, Christopher Witte wrote:
> >
> > I had export working using XeLaTeX using the instructions from the
> > FAQ >(with
> > some slight modifications), but after upgrading to the new export it
> > isn't working.  It appears the hook
> > org-export-latex-after-initial-vars-hook isn't defined anymore.
> >
> > Any advice on what I need to change to get it to work?
>
> I have noticed discussions on this before and I fail to understand the
> need for all the setup mentioned in the above Worg entry.  I use XeLaTeX
> almost exclusively, and all I have is something like this:
>
>   ;;; XeLaTeX customisations
>   ;; remove "inputenc" from default packages as it clashes with xelatex
>   (setf org-latex-default-packages-alist
> (remove '("AUTO" "inputenc" t) org-latex-default-packages-alist))
>
>   (add-to-list 'org-latex-packages-alist '("" "xltxtra" t))
>   ;; choose Linux Libertine O as serif and Linux Biolinum O as sans-serif
> fonts
>   (add-to-list 'org-latex-packages-alist '("" "libertineotf" t))
>
>   ;; org to latex customisations, -shell-escape needed for minted
>   (setq org-export-dispatch-use-expert-ui t ; non-intrusive export dispatch
> org-latex-pdf-process   ; for regular export
> '("xelatex -shell-escape -interaction nonstopmode
> -output-directory %o %f"
>   "xelatex -shell-escape -interaction nonstopmode
> -output-directory %o %f"
>   "xelatex -shell-escape -interaction nonstopmode
> -output-directory %o %f"))
>
> For beamer export I add this line:
>
>   #+LaTeX_HEADER: \setsansfont{Linux Biolinum O}
>
> So far I have not encountered any problems.  Although I have to say, I
> do not use unicode in mathmode.
>
> I am curious to know why others need all this elaborate setup to use
> XeLaTeX.
>
> Cheers,
>
> --
> Suvayu
>
> Open source is the future. It sets us free.
>
>

Re: [O] refine org-babel-tangle-jump-to-org?

[Rainer M. Krug]

Eric Schulte  writes:

> rai...@krugs.de (Rainer M. Krug) writes:
>
>> Hi
>>
>> I am using  org-babel-tangle-jump-to-org when debugging code written in
>> org and tangled. I have some longisch code blocks and it is always
>> irritating, as it only jumps to the codde block. Would it be possible to
>> extend the function, that it jumps to the line of the code?
>> That would make this funktion much more user friendly.
>>
>
> I've just pushed up a change which should make this change.  I tested
> this against the example.C file tangled from the attached Org-mode file.

Thanks - works much better now.
Very nice - it jumps even to the location in an indirect buffer -
perfect.

Without trying to be a perfectionist, it is in most cases between one
and three lines off.

Is this only in y case? If yes, please let me know and I can send you an
org file privately.

It would be really nice, if it would be possible to put the cursor on
the same line, preferably same character? But it is definitely usable
like this for debugging.

>
> * example
>   :PROPERTIES:
>   :tangle:   yes
>   :comments: link
>   :END:
>
> The required headers.
> #+name: header
> #+begin_src C
>   #include 
> #+end_src
>
> Here is the auxiliary function.
> #+name: auxiliary
> #+begin_src C
>   void aux(char* arg){
> printf("first argument: %s\n", arg);
>   }
> #+end_src
>
> Here is the main function.
> #+name: main
> #+begin_src C
>   int main(int argc, char *argv[])
>   {
> aux(argv[1]);
> return 0;
>   }
> #+end_src
>
>
> While implementing this change I did notice that this jumping
> functionality only appears to work with linked code blocks, 

linked code blocks? Do you mean the header argument :comments link or,
as I use :comments yes? If I remember correctly, when you announced this
function, you explicitly mentioned that :comments yes is required for it
to work?


Thanks a lot,

Rainer

>which should
> I believe is a bug.
>
> Best,
>
>>
>> Thanks,
>>
>> Rainer

-- 
Rainer M. Krug


pgp01bgUR4C0d.pgp
Description: PGP signature

Re: [O] de-tangle function?

[Rainer M. Krug]

Rasmus  writes:

> "Sebastien Vauban" 
> writes:
>
>>> Does it work reliably?
>>
>> You need the code blocks to be wrapped into comments for it to work.
>>
>> Regarding reliability, it does work well on small examples. I remember having
>> had really bad results with my huge .emacs file, but hadn't any time to debug
>> the problem -- try to reproduce -- at that time.
>>
>> So, when you do it, please keep a backup of your original Org file. It's
>> safer.
>>
>> But, if there are bugs, they should be clearly identified, and fixed...
>
> It not always good at finding its way back into the Org file, and I
> found that some of the header arguments didn't 'work properlyø for
> 'complicated' blocks.  I'll see if I can make reproducible examples
> later.
>
> It's definitely a potentially cool feature though.  Notice you have to
> run it from the tangled file.

Absolutely - especially debugging code (in my case R) would be easier.

Cheers,

Rainer
>
> –Rasmus

-- 
Rainer M. Krug


pgplMsfWb_sI7.pgp
Description: PGP signature

Re: [O] de-tangle function?

[Rainer M. Krug]

<#secure method=pgpmime mode=sign>

"Sebastien Vauban" 
writes:

> Hi Rainer,
>
> Rainer M. Krug wrote:
>> I remember something about a de-tangle function, which re-imports the
>> source code blocks into the org file is previously tangled with comments
>> et al, but I can't find that function any more.
>>
>> Is it still there?
>
> M-x org-babel-detangle

How did I miss that

>
>> Does it work reliably?
>
> You need the code blocks to be wrapped into comments for it to work.
>
> Regarding reliability, it does work well on small examples. I remember having
> had really bad results with my huge .emacs file, but hadn't any time to debug
> the problem -- try to reproduce -- at that time.
>
> So, when you do it, please keep a backup of your original Org file. It's
> safer.

Pity - then I can't use it. I have a long org file which tangles in many
.R files and in many cases one file spans across many blocks. I have to
trust it when using it at this stage. But as Eric has improved the
org-babel-tangle-jump-to-org function, I will use that one in debugging.

>
> But, if there are bugs, they should be clearly identified, and fixed...

I agree - but unfortunately at the moment I won't be able to help here.

Cheers,

Rainer

>
> Best regards,
>   Seb

-- 
Rainer M. Krug