[O] org-mobile: how to get rid of .org file?

[Nikolaus Rath]

Hello,

I accidentally created a file 'from_mobile.org' (different from the
'org-mobile.org' used by org-mobile) in my org-directory. On the next
org-mobile-push, this file got copied into my org-mobile-directory and
now shows up on my mobile (Android) device.

I then deleted the "from_mobile.org" from org-directory and executed
org-mobile-push again. However, the copy in org-mobile-directory
persists and (probably for that reason) also continues to show up on my
phone.

Why isn't org-mobile picking up that the file has been removed?

Thanks!
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

 »Time flies like an arrow, fruit flies like a Banana.«

[O] Bug: sas comments in source blocks confused with headings [8.2.10 (8.2.10-35-g19a7d6-elpaplus @ ~/.emacs.d/elpa/org-plus-contrib-20150406/)]

[Kyle Andrews]

I included SAS code for reference in an org file and noticed that a SAS
comment breaks the folding feature. The buffer is folded only until the
comment. The snippet below placed in an org-buffer should clarify what I
mean.

<

** SAS

#+BEGIN_SRC sas
* a full line comment in SAS code;
proc mixed method=reml cl;
class D M G;
model y = M G M*G;
random D D*M D*G/cl alpha=0.05;  /* can't do 3-way */
lsmeans M G M*G/cl adjust=tukey; /* only fixed effects */
run;
#+END_SRC

** R

Here is how to fit the mixed effect model in R.

>

If you press tab on the SAS heading, it doesn't fold all the way to the
R heading, but only to the comment line. Perhaps this is fixed in org
8.3?

---


Emacs  : GNU Emacs 24.4.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.14.7)
 of 2015-01-17 on bisson
Package: Org-mode version 8.2.10 (8.2.10-35-g19a7d6-elpaplus @
/home/k/.emacs.d/elpa/org-plus-contrib-20150406/)

current state:
==
(setq
 org-drill-optimal-factor-matrix '((1 (2.6 . 4.14)))
 org-tab-first-hook '(org-hide-block-toggle-maybe
org-src-native-tab-command-maybe
  org-babel-hide-result-toggle-maybe
org-babel-header-arg-expand)
 org-adapt-indentation nil
 org-speed-command-hook '(org-speed-command-default-hook
org-babel-speed-command-hook)
 org-occur-hook '(org-first-headline-recenter)
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-html-format-drawer-function '(lambda (name contents) contents)
 org-latex-format-inlinetask-function 'ignore
 org-confirm-shell-link-function 'yes-or-no-p
 org-image-actual-width nil
 org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
 org-agenda-inhibit-startup t
 org-pretty-entities 1
 org-latex-format-headline-function
'org-latex-format-headline-default-function
 org-default-notes-file "~/org/notes.org"
 org-after-todo-state-change-hook '(org-clock-out-if-current)
 org-latex-format-drawer-function '(lambda (name contents) contents)
 org-capture-mode-hook '(make-frame)
 org-from-is-user-regexp nil
 org-src-mode-hook '(org-src-babel-configure-edit-buffer
org-src-mode-configure-edit-buffer)
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-babel-pre-tangle-hook '(save-buffer)
 org-font-lock-set-keywords-hook '(org-drill-add-cloze-fontification)
 org-mode-hook '(#[nil "\300\301\302\303\304$\207"
   [org-add-hook change-major-mode-hook org-show-block-all
append local] 5]
 #[nil "\300\301\302\303\304$\207"
   [org-add-hook change-major-mode-hook
org-babel-show-result-all append local] 5]
 org-babel-result-hide-spec org-babel-hide-all-hashes)
 org-ascii-format-drawer-function '(lambda (name contents width) contents)
 org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point
org-babel-execute-safely-maybe)
 org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
  org-cycle-hide-inline-tasks org-cycle-show-empty-lines
  org-optimize-window-after-visibility-change)
 org-startup-with-latex-preview t
 org-latex-packages-alist '(("" "multirow" t) ("" "fontenc" t) (""
"siunitx" t) ("" "xfrac" t)
("" "mathtools" t) ("" "physics" t) ("" "color"
t))
 org-babel-tangle-lang-exts '(("maxima" . "max") ("julia" . "jl") ("tcl" .
"tcl") ("python" . "py")
  ("perl" . "pl") ("latex" . "tex")
("emacs-lisp" . "el"))
 org-confirm-elisp-link-function 'yes-or-no-p
 org-startup-with-inline-images t
 org-metadown-hook '(org-babel-pop-to-session-maybe)
 org-babel-after-execute-hook '(org-display-inline-images)
 org-html-format-headline-function 'ignore
 org-babel-load-languages '((emacs-lisp . t) (calc . t) (sh . t) (latex .
t) (R . t) (perl . t)
(octave . t) (python . t) (scheme . t)
(makefile . t) (tcl . t)
(julia . t) (maxima . t))
 org-html-format-inlinetask-function 'ignore
 org-fontify-whole-heading-line t
 org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
 org-confirm-babel-evaluate nil
 org-src-fontify-natively t
 )

Re: [O] Proper syntax for org-reveal-* local variables?

[John Hendy]

On Sun, Apr 12, 2015 at 6:04 PM, John Hendy  wrote:
> Hello,
>
>
> Giving a first shot (at least in a while) with org-reveal and am
> struggling a little with the options allowable in Reveal.initialize({
> }). The github repo readme discusses custom variables for this purpose
> in the "Configure Plug-Ins" section:
> - https://github.com/yjwen/org-reveal
>
> In hunting around, I'm not sure what they specific syntax should be? I've 
> tried:
>
>
> # -*- org-reveal-center: nil -*- (after my other #+options, etc. stuff)
>
> I also tried (at the end of the file):
>
> # Local Variables:
> # org-reveal-center: nil
> # End:

This looks to have worked after all, though it required confirming
allowing it. I had both a Local Variables section as well as #+bind
and # -*- [...] -*- in my preamble. When I deleted those two lines, I
used C-c C-c to refresh and it asked me to allow the Local Variables
setting.

In a quick re-skim of the documentation I find googling "org-mode
'Local Variables:'", I'm not seeing anything about C-c C-c. The
closest I get is the org-mode man page for in-buffer settings, but it
isn't obvious to me that local variables are in the same category from
reading that. Am I looking in the wrong place?


Best regards,
John


>
> In checking the resultant .html output, the contents of
> Reveal.initialize still contains =center: true,=, so something isn't
> working properly.
>
>
> Thanks for any suggestions,
> John

[O] Proper syntax for org-reveal-* local variables?

[John Hendy]

Hello,


Giving a first shot (at least in a while) with org-reveal and am
struggling a little with the options allowable in Reveal.initialize({
}). The github repo readme discusses custom variables for this purpose
in the "Configure Plug-Ins" section:
- https://github.com/yjwen/org-reveal

In hunting around, I'm not sure what they specific syntax should be? I've tried:


# -*- org-reveal-center: nil -*- (after my other #+options, etc. stuff)

I also tried (at the end of the file):

# Local Variables:
# org-reveal-center: nil
# End:

In checking the resultant .html output, the contents of
Reveal.initialize still contains =center: true,=, so something isn't
working properly.


Thanks for any suggestions,
John

Re: [O] [Feature Request] [ENTER] or [C-Alt ENTER] while on headline skip over drawers automatically

[Nicolas Goaziou]

Rasmus  writes:

> I had a patch a while ago adding support for M-RET on keywords.  This
> could be pushed together with a documentation on how to use it with
> add-function (is nadvice.el too new for us to assume when writing
> documentation?) or the mentioned hook.

We still have to think about how to dispatch commands between M-RET and
C-RET.

Regards,

Re: [O] [Feature Request] [ENTER] or [C-Alt ENTER] while on headline skip over drawers automatically

[Rasmus]

Nicolas Goaziou  writes:

> Rasmus  writes:
>
>> Nicolas Goaziou  writes:
>>
>>> Eventually, we could introduce a `org-return-hook' where an user could
>>> add, e.g.,
>>>
>>>   (lambda () (when (org-at-heading-p) (org-end-of-meta-data) (insert
>>>   "\n")))
>>>
>>> Opinions?
>>
>> +1.
>>
>> I'd also like a hook on C-RET.
>
> Actually, a hook isn't even needed if you use `advice-add'.

There's also org-metareturn-hook.

I had a patch a while ago adding support for M-RET on keywords.  This
could be pushed together with a documentation on how to use it with
add-function (is nadvice.el too new for us to assume when writing
documentation?) or the mentioned hook.

—Rasmus

-- 
However beautiful the theory, you should occasionally look at the evidence

Re: [O] [Feature Request] [ENTER] or [C-Alt ENTER] while on headline skip over drawers automatically

[Nicolas Goaziou]

Rasmus  writes:

> Nicolas Goaziou  writes:
>
>> Eventually, we could introduce a `org-return-hook' where an user could
>> add, e.g.,
>>
>>   (lambda () (when (org-at-heading-p) (org-end-of-meta-data) (insert
>>   "\n")))
>>
>> Opinions?
>
> +1.
>
> I'd also like a hook on C-RET.

Actually, a hook isn't even needed if you use `advice-add'.


Regards,

Re: [O] Bug of "org-export radio targets" with utf-8 characters

[Nicolas Goaziou]

Hello,

 writes:

> <<中文字符>> and <<<片仮名>>> can’t be exported correctly whether in latex or html. 
>
> It seems to be the problem of function “org-export-solidify-link-text”……
>
>
> So, I change the function “org-export-solidify-link-text”  in ox.el with the 
> codes below
>
>
> (defun org-export-solidify-link-text (s)
>   "Take link text S and make a safe target out of it."
>   (save-match-data
> (mapconcat 'identity (org-split-string (prin1-to-string
> (encode-coding-string s 'utf-8)) "[^a-zA-Z0-9_.-:]+") "-")))

Thanks. 

Actually, the real solution is to erase `org-export-solidify-link-text'
altogether. It is a source of problems. I will look into it.

Regards,

-- 
Nicolas Goaziou

Re: [O] org-latex question

[Nicolas Goaziou]

Hello,

Marcin Borkowski  writes:

> True.  This is because org-latex-headline is written this way:
>
> ,
> | (if (and numberedp opt-title
> | ;;   ^^^ ^ why this?  Maybe there's a good reason...
> |(not (equal opt-title full-text))
> |(string-match "\\`\\(.*?[^*]\\){" section-fmt))
> |   (...)
> | ;; Impossible to add an alternative heading.  Fallback to
> | ;; regular sectioning format string.
> | (format section-fmt full-text
> | (concat headline-label pre-blanks contents)))
> `
>
> However, it need not be this way: LaTeX itself (or more precisely: the
> default classes) seem to support the alt-title even for starred
> sectioning commands.

I removed NUMBEREDP, since I cannot remember the reason for its
presence.

> Also, another way to circumvent this (/if/ there is some deep reason for
> the above code which I don't see, which is quite probable) is to hack
> into this part of the let form in org-latex-headline:
>
> ,
> | (section-back-end
> | (org-export-create-backend
> |  :parent 'latex
> |  :transcoders
> |  '((underline . (lambda (o c i) (format "\\underline{%s}" c))
> `
>
> and apply a (smart enough) filter in the (auxiliary) section-back-end,
> something like removing a match for
>
> \\footnote{.*?}
>
> (this would be easy to break; in general, regexen are not a suitable
> tool for this, because they can't "count" and match braces; however,
> writing a suitable filter should not be extremely difficult).

Or ignore completely footnotes-references in the anonymous back-end.
However, is it needed since :ALT_TITLE: is now supported for all
headlines? I'm not sure.


Regards,

-- 
Nicolas Goaziou

[O] check boxes not completing for TODO SUBTASKS AND SUBSUBTASKS

[Sharon Kimble]

I have a org-mode setup for a latex file that I am writing, and it
is organised like this for its TODOs -

--8<---cut here---start->8---
** latex
*** foobar 2015 [0/2] [0%]=MAIN FOOBAR
 TODO finish putting in all the details from a bare glance=TASKS
 TODO urls in the drawer
:project-urls: 
https://nccih.nih.gov/health/foo.htm
https://en.wikipedia.org/wiki/foo
* TODO foobar1=SUBTASKS
** TODO from foo.com=SUBSUBTASKS
--8<---cut here---end--->8---

There are 7 :project-urls: in the drawer, with 27 SUBTASKS, each of
which has 7 SUBSUBTASKS.

How can I get an overall project total in the checkboxes at MAIN
FOOBAR please? I've tried "C-c #" but its made no difference.

Thanks
Sharon.
-- 
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
Debian testing, fluxbox 1.3.7, emacs 24.4.1.0


signature.asc
Description: PGP signature

Re: [O] [PATCH]Extend export hook example for removing headlines with tagignore_heading

[Rasmus]

Hi,

Thanks for the patch. I have not read it as I'm on the mobile.

What is the difference between your patch and org-export-ignore-headlines in
ox-extra?

If you want the functionality in ox.el you should write a solution that uses
a property like UNNUMBERED. It's however a non-trivial problem as discussed
on the org-hacks worg page. This is, IMO, the right way to tackle this
issue, if it is an issue.

Skimming the so answer you link to your suggestion is not robust for ignored
headlines following a no export headline.


Rasmus

Re: [O] org-latex question

[Vikas Rawal]

> 
>>> See :ALT_TITLE: property.
>>> 
>> 
>> ALT_TITLE seems to work only for those headlines that appear in the
>> Table of Contents. While that is the main purpose, this does not have
>> to be necessarily the case. In the present case, I need it because
>> LaTeX would not accept a footnote to a heading without it.
> 
> It seems that the bug is either
> 
>   1. That the footnote that is written out at all.  If you call
>  org-footnote-action (or whatever C-c C-x f is) you are told that
>  footnotes are not supported in headings
> 
This has been fixed today by Nicolas. There is another thread on the mailing 
list discussing this. So if you update orgmode, this would go.

>   2. The optional argument of the \section-like command should
>  automatically be set either :ALT_TITLE or :title sans the footnote
>  if a footnote is present.
> 
Yes, this needs to be implemented, it seems.


Vikas

Re: [O] org-latex question

[Rasmus]

Hi,

>> See :ALT_TITLE: property.
>> 
>
> ALT_TITLE seems to work only for those headlines that appear in the
> Table of Contents. While that is the main purpose, this does not have
> to be necessarily the case. In the present case, I need it because
> LaTeX would not accept a footnote to a heading without it.

It seems that the bug is either

   1. That the footnote that is written out at all.  If you call
  org-footnote-action (or whatever C-c C-x f is) you are told that
  footnotes are not supported in headings

   2. The optional argument of the \section-like command should
  automatically be set either :ALT_TITLE or :title sans the footnote
  if a footnote is present.

—Rasmus

-- 
Vote for proprietary math!

[O] [PATCH]Extend export hook example for removing headlines with tag ignore_heading

[Ondřej Grover]

Hello,

I've attached a patch for the Advanced configuration (for exporting)
chapter of the Org mode manual that extends the hook example there to
provide the commonly requested ignoreheading-like functionality found in
the Beamer backend. The example is very simple and adds just one line of
code to the function thanks to the MATCH argument of the `org-map-entries`
function.
The commit message contains the TINYCOMMIT cookie as I'm not a FSF member.

Originally I only intended this solution to be an answer to questions on
StackOverflow that did not help me much (
http://stackoverflow.com/a/29588450/4779220), but I think it is something
very commonly requested and should be documented and easily accessible.

How I discovered this solution:
I've always liked the `ignoreheading` tag functionality in Beamer export. I
wanted to have something like it for all export backends.
The solutions I found on the Internet either didn't work or were filter
based which did not remove the headline nodes in the parsed structure.
So I decided to make my own solution. I found the hook example for removing
all headlines before processing in the Org manual. That was almost what I
wanted, but I needed to limit it to headlines with a tag. I had a look at
the documentation of the `org-map-entries` function and discovered the
MATCH argument that can match tags like in agenda views. So in the end I
added just 1 line of code to the example.

This experience once again showed me that Emacs truly is an extensible
self-documenting editor. I'd like to express my gratitude to all the
contributors of Emacs and Org mode.

Kind regards,
Ondřej Grover
From 1e19e5174e21e8ddfd96ed5da5c2cbbb444e9d16 Mon Sep 17 00:00:00 2001
From: Ondrej Grover 
Date: Sun, 12 Apr 2015 13:43:31 +0200
Subject: [PATCH] org.texi: Extend export hook example with ignore_heading tag
 support

* doc/org.texi (Advanced configuration): Extend the pre-processing
export hook example to support similar (but simpler and more general)
functionality like that provided by the ignoreheading tag in the
Beamer export backend.  This is a commonly requested snippet and the
Internet is full of much worse and broken solutions, so the manual
should show the recommended solution.

TINYCHANGE
---
 doc/org.texi | 23 ++-
 1 file changed, 14 insertions(+), 9 deletions(-)

diff --git a/doc/org.texi b/doc/org.texi
index c400f77..8dc0a92 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -13811,24 +13811,29 @@ one, @code{org-export-before-processing-hook} is called before expanding
 macros, Babel code and include keywords in the buffer.  The second one,
 @code{org-export-before-parsing-hook}, as its name suggests, happens just
 before parsing the buffer.  Their main use is for heavy duties, that is
-duties involving structural modifications of the document.  For example, one
-may want to remove every headline in the buffer during export.  The following
-code can achieve this:
+duties involving structural modifications of the document. For example, one
+may want to remove every headline with the @samp{ignore_heading} tag in the
+buffer during export.  The following code can achieve this:
 
 @lisp
 @group
-(defun my-headline-removal (backend)
-  "Remove all headlines in the current buffer.
+(defun ignored-headlines-removal (backend)
+  "Remove all headlines with the ignore_headline tag in the current buffer.
 BACKEND is the export back-end being used, as a symbol."
   (org-map-entries
-   (lambda () (delete-region (point) (progn (forward-line) (point))
+   (lambda () (delete-region (point) (progn (forward-line) (point
+   "ignore_heading"))
 
-(add-hook 'org-export-before-parsing-hook 'my-headline-removal)
+(add-hook 'org-export-before-parsing-hook 'ignored-headlines-removal)
 @end group
 @end lisp
 
-Note that functions used in these hooks require a mandatory argument,
-a symbol representing the back-end used.
+The second argument to the @code{org-map-entries} function is an agenda-style
+match query string. Note the underscore in the tag, it is not recommended to
+use the @samp{ignoreheading} tag because the Beamer export backend treates it
+in a similar, yet more complicated way.  Also note that functions used in
+these hooks require a mandatory argument, a symbol representing the back-end
+used.
 
 @subheading Filters
 
-- 
2.1.4

Re: [O] org-latex question

[Marcin Borkowski]

On 2015-04-12, at 10:59, Vikas Rawal  wrote:

>>> How do I get a headline to be exported like this?
>>> 
>>> 
>>> \section[Effect on staff turnover]{An analysis of the
>>> effect of the revised recruitment policies on staff
>>> turnover at divisional headquarters}
>>> 
>>> 
>>> That is, with an extra short-title to be used in Table of Contents and
>>> other running heads?
>> 
>> See :ALT_TITLE: property.
>> 
>
> ALT_TITLE seems to work only for those headlines that appear in the Table of 
> Contents. While that is the main purpose, this does not have to be 
> necessarily the case. In the present case, I need it because LaTeX would not 
> accept a footnote to a heading without it.

True.  This is because org-latex-headline is written this way:

,
| (if (and numberedp opt-title
| ;;   ^^^ ^ why this?  Maybe there's a good reason...
|  (not (equal opt-title full-text))
|  (string-match "\\`\\(.*?[^*]\\){" section-fmt))
| (...)
|   ;; Impossible to add an alternative heading.  Fallback to
|   ;; regular sectioning format string.
|   (format section-fmt full-text
|   (concat headline-label pre-blanks contents)))
`

However, it need not be this way: LaTeX itself (or more precisely: the
default classes) seem to support the alt-title even for starred
sectioning commands.

Also, another way to circumvent this (/if/ there is some deep reason for
the above code which I don't see, which is quite probable) is to hack
into this part of the let form in org-latex-headline:

,
| (section-back-end
|   (org-export-create-backend
|:parent 'latex
|:transcoders
|'((underline . (lambda (o c i) (format "\\underline{%s}" c))
`

and apply a (smart enough) filter in the (auxiliary) section-back-end,
something like removing a match for

\\footnote{.*?}

(this would be easy to break; in general, regexen are not a suitable
tool for this, because they can't "count" and match braces; however,
writing a suitable filter should not be extremely difficult).

> Vikas

Hth,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University

Re: [O] org-latex question

[Vikas Rawal]

> 
>> How do I get a headline to be exported like this?
>> 
>> 
>> \section[Effect on staff turnover]{An analysis of the
>> effect of the revised recruitment policies on staff
>> turnover at divisional headquarters}
>> 
>> 
>> That is, with an extra short-title to be used in Table of Contents and
>> other running heads?
> 
> See :ALT_TITLE: property.
> 

ALT_TITLE seems to work only for those headlines that appear in the Table of 
Contents. While that is the main purpose, this does not have to be necessarily 
the case. In the present case, I need it because LaTeX would not accept a 
footnote to a heading without it.

Vikas

[O] How to exclude completed daily tasks from the agenda view

[Marcin Borkowski]

Hi list,

I have a number of TODO items that should be done *every day*.  I do not
use Org-mode for them, since in the two-week agenda they tend to clutter
all days, not only today; if I complete such task, I want it not to be
visible in the agenda /at all/.

Is there a way to overcome this?  One way would be to gather these tasks
in a subtree, give it a special tag (or preferably, a category), and
define a custom agenda view /excluding/ this particular tag/category.
Is that possible?  I tried this

(setq org-agenda-custom-commands
  '(("X" agenda "-mytag")))

but it didn't work as expected.  I also saw somewhere the
`org-agenda-skip-function' variable; would this be a good way?  If yes,
how to use it?  Do I get it correctly that it is a parameterless
function, called with point at some entry?  Also, I saw the
`org-agenda-skip-regexp' variable; maybe this is the way to go?  Or
maybe I should put `org-agenda-skip-if' into `org-agenda-skip-function'?

TIA,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University

Re: [O] make code lines bold in export

[thomas]

On 12.04.2015 10:20, thomas wrote:

Hi John,

thank you for your quick reply. I have to admit to do this at the 
moment would be way over my head ...


I found an easy method to boldify inline code here: 
http://orgmode.org/Changes.html





New option: org-babel-inline-result-wrap


If you set this to the following

(setq org-babel-inline-result-wrap "$%s$")

then inline code snippets will be wrapped into the formatting string.



this is already something; matches about 50% of the cases where I need 
to boldify code  :-)


thanks,
thomas



On 08.04.2015 15:45, John Kitchin wrote:

A filter is what I would use. You could get the src block text and
replace lines with that comment in them for the output. This post is not
exactly that, but it has the idea of how to do it. you would get the
text, modify it, and return the new modified text.

http://kitchingroup.cheme.cmu.edu/blog/2013/09/30/Attaching-code-blocks-to-a-pdf-file-during-export/

thomas writes:


Hi,

it would be very nice if i was able to highlight (i.e. make bold)
certain lines in an exported code, say ODT.

Something like this:

#+BEGIN_SRC java
public class HelloActivity extends Activity {
/** Called when the activity is first created */
@Override
public void onCreate(Bundle savedInstanceState)
{
  super.onCreate(savedInstanceState);
  setContentView(R.layout.main);  // *MAKE THIS LINE BOLD*
}
}
#+END_SRC

Is there an - easy - way to do this? My first guess: I need to write an
export filter ...  what would you think?

Thanks,
thomas

--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu

[O] org-sort for non-En entries

[Gour]

Hello,

after resolving some issues with broken *.vcf files I was able to import my
contacts into org-mode via org-vcard and then wanted to sort entries which
contain Croatian characters.

However, org-sort does sort according to the English rules and the entries
containing Croatian chars are put at the end, after 'Z' entries.

What I need to do in order to get the contacts list sorted according to
Croatian alphabet: A,B,C,Č,Ć,D,Dž,Đ,..S,Š,..Z,Ž ?


Sincerely,
Gour

-- 
The senses are so strong and impetuous, O Arjuna, 
that they forcibly carry away the mind even of a man 
of discrimination who is endeavoring to control them.

Re: [O] org-latex question

[Nicolas Goaziou]

Hello,

Vikas Rawal  writes:

> How do I get a headline to be exported like this?
>
>
> \section[Effect on staff turnover]{An analysis of the
> effect of the revised recruitment policies on staff
> turnover at divisional headquarters}
>
>
> That is, with an extra short-title to be used in Table of Contents and
> other running heads?

See :ALT_TITLE: property.


Regards,

-- 
Nicolas Goaziou