Re: [O] Exporting org-mode source

[Vikas Rawal]

> 
> Vikas Rawal  agrarianresearch.org> writes:
> 
> 
>> I think I could not express my objective clearly.I want the org code block 
> to be exported literally. 
> 
> 
> Indent lines that begin with *, is this what you want?

I am not exactly sure what you are suggesting. The block below does not work 
for me. It is not exported literally.


> #+BEGIN_SRC org
> ** What are the major disputes in the literature
> *** adulterated text
> Instrument cultivated alteration any favourable expression law far
> nor. Both new like tore but year. An from mean on with when sing pain.
> Oh to as principles devonshire companions unsatiable an delightful.
> The ourselves suffering the sincerity. Inhabit her manners adapted age
> certain. Debating offended at branched striking be subjects.
> #+END_SRC
> 
> 

Vikas

Re: [O] First attempt at exporting to PDF.

[Sharon Kimble]

Thanks for this John, replies in line -
John Kitchin  writes:

> you should be able to get references with \cite{key1} and \cite{key2}.
> where key1 and key2 are bibtex keys in a bibtex file called
> references.bib.

I now have references showing in the document as "[\cite{10}]" where
10 is a specified entry in the "references.bib" database. I've put
it in square brackets so that when it appears in the document then
it appears as [10].

Having these as headers helps too
--8<---cut here---start->8---
# -*- mode:org; mode:reftex; indent-tabs-mode:nil; tab-width:2 -*-
#+STARTUP: content
#+LATEX_CLASS: article
#+LATEX_CLASS_OPTIONS: [a4paper]
#+OPTIONS: toc:t
#+OPTIONS: ^:{}
#+TITLE: The custard pie mystery.
#+AUTHOR: Sharon Kimble & Sarah ?
#+LINK: notes #%s
#+LATEX_HEADER: \usepackage[hyperref,x11names]{xcolor}
#+LATEX_HEADER: 
\usepackage[colorlinks=true,urlcolor=SteelBlue4,linkcolor=Firebrick4]{hyperref}
#+LaTeX_HEADER: \usepackage[backend=biber,style=verbose]{biblatex}
#+LaTeX_HEADER: \bibliography{/home/boudiccas/.emacs.d/research/references.bib}
#+LaTeX_HEADER: \usepackage{bussproofs}
#+LaTeX_HEADER: \usepackage{amsmath,amssymb,amsopn}
#+LaTeX_HEADER: \usepackage{graphicx}
#+LaTeX_HEADER: \usepackage{makeidx} %robustindex % Indexing
#+LaTeX_HEADER: \usepackage[british]{babel} % For british english hyphenation 
patterns
#+LaTeX_HEADER: \usepackage{fancyhdr} % Change caption style; changes headers 
and page styles
--8<---cut here---end--->8---


> you need at the end of your org-file where you want the bibliography
> to appear:
>
> \bibliographystyle{unsrt}
> \bibliography{references}

I have
--8<---cut here---start->8---
* Bibliography
\bibliographystyle{plain}
\bibliography{references}
--8<---cut here---end--->8---
But all it shows in the pdf is
╭
│* Bibliography
│
│references
╰

>
> In your init file, you may need to do this:
> ;; for minted you must run latex with -shell-escape because it calls
> pygmentize as an external program
> (setq org-latex-pdf-process
> '("pdflatex -shell-escape -interaction nonstopmode -output-directory
> %o %b"
> "bibtex %b"
> "pdflatex -shell-escape -interaction nonstopmode -output-directory %o
> %b"
> "pdflatex -shell-escape -interaction nonstopmode -output-directory %o
> %b"))
>
> I do not think org-mode runs bibtex by default. After that you should
> see the references.

I'm not sure what you mean by "minted" but I've included it in my
"setup-testbed.el" at the end, where all new testing code goes, but
I don't see what difference its made.

This is one of the bibliographic references from its database
--8<---cut here---start->8---
@Article{,
  author =   {MacRae K. Pattison J.},
  title ={Home chemotherapy.},
  journaltitle = {Nursing Times},
  ALTyear =  {2002},
  OPTkey =   {8},
  OPTvolume ={98},
  OPTnumber ={35},
  OPTpages = {34-35},
}
--8<---cut here---end--->8---
Where 'key' is actually displayed as "OPTkey", does that make a
difference please?

Thanks
Sharon.
>
> John
>
> ---
> John Kitchin
> Associate Professor
> Doherty Hall A207F
> Department of Chemical Engineering
> Carnegie Mellon University
> Pittsburgh, PA 15213
> 412-268-7803
> http://kitchingroup.cheme.cmu.edu
>
> On Sat, May 3, 2014 at 4:00 PM, Thomas S. Dye  wrote:
>
> Aloha Sharon,
> 
> 
> Sharon Kimble  writes:
> 
> >> I have never tried what you are trying to do with references so
> >> someone
> >> else must step in and help you there.
> >
> > Just hope someone steps up to the plate?
> 
> 
> This was written for the old exporter, but it might be useful to
> you:
> 
> http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-17
> 
> Also, the BibTeX entry in your original post was mal-formed. It
> lacked
> a key and the author field looked wrong, IIRC. You might want to
> check out
> the BibTeX file format:
> 
> http://www.bibtex.org/Format/
> 
> hth,
> Tom
> 
> --
> Thomas S. Dye
> http://www.tsdye.com
> 
> 
>
>

-- 
A taste of linux = http://www.sharons.org.uk
my git repo = https://bitbucket.org/boudiccas/dots
TGmeds = http://www.tgmeds.org.uk
Debian testing, Fluxbox 1.3.5, emacs 24.4.50.19


signature.asc
Description: PGP signature

Re: [O] Exporting org-mode source

[Han Fan]

Vikas Rawal  agrarianresearch.org> writes:

> 
> > 
> > Vikas Rawal  agrarianresearch.org> writes:
> > 
> > 
> >> I think I could not express my objective clearly.I want the org code 
block 
> > to be exported literally. 
> > 
> > 
> > Indent lines that begin with *, is this what you want?
> 
> I am not exactly sure what you are suggesting. The block below does not 
work for me. It is not exported literally.
> 
> > #+BEGIN_SRC org
> > ** What are the major disputes in the literature
> > *** adulterated text
> > Instrument cultivated alteration any favourable expression law far
> > nor. Both new like tore but year. An from mean on with when sing pain.
> > Oh to as principles devonshire companions unsatiable an delightful.
> > The ourselves suffering the sincerity. Inhabit her manners adapted age
> > certain. Debating offended at branched striking be subjects.
> > #+END_SRC
> > 
> > 
> 
> Vikas
> 
> 
There is a white space before *, but I didn't see that in your quote, is
that because of your newsgroup reader client?
See the link below:
http://article.gmane.org/gmane.emacs.orgmode/85805
Lines start with * is exported to headings only when there is no white
space before *.

Sorry for my broken English.

Re: [O] Exporting org-mode source

[Fletcher Charest]

Hi,

Sorry if I misunderstood... If you create an Org source block like this
with nothing inside:

#+begin_src org

#+end_src

...then, with your cursor inside, enter it with C-c ', write your org tree,
and validate with C-c ' again, then export... Does it do what you want?

FC



On Sun, May 4, 2014 at 10:04 AM, Vikas Rawal <
vikasli...@agrarianresearch.org> wrote:

> >
> > Vikas Rawal  agrarianresearch.org> writes:
> >
> >
> >> I think I could not express my objective clearly.I want the org code
> block
> > to be exported literally.
> >
> >
> > Indent lines that begin with *, is this what you want?
>
> I am not exactly sure what you are suggesting. The block below does not
> work for me. It is not exported literally.
>
>
> > #+BEGIN_SRC org
> > ** What are the major disputes in the literature
> > *** adulterated text
> > Instrument cultivated alteration any favourable expression law far
> > nor. Both new like tore but year. An from mean on with when sing pain.
> > Oh to as principles devonshire companions unsatiable an delightful.
> > The ourselves suffering the sincerity. Inhabit her manners adapted age
> > certain. Debating offended at branched striking be subjects.
> > #+END_SRC
> >
> >
>
> Vikas
>

Re: [O] Exporting org-mode source

[Han Fan]

Fletcher Charest  writes:

> Hi,
>
> Sorry if I misunderstood... If you create an Org source block like this with 
> nothing inside:
>
> #+begin_src org
>
> #+end_src
>
> ...then, with your cursor inside, enter it with C-c ', write your org tree, 
> and validate with C-c ' again, then export... Does it do
> what you want?
>
> FC
>
> On Sun, May 4, 2014 at 10:04 AM, Vikas Rawal 
>  wrote:
>
> >
> > Vikas Rawal  agrarianresearch.org> writes:
> >
> >
> >> I think I could not express my objective clearly.I want the org code 
> block
> > to be exported literally.
> >
> >
> > Indent lines that begin with *, is this what you want?
>
> I am not exactly sure what you are suggesting. The block below does not 
> work for me. It is not exported literally.
>
> > #+BEGIN_SRC org
> > ** What are the major disputes in the literature
> > *** adulterated text
> > Instrument cultivated alteration any favourable expression law far
> > nor. Both new like tore but year. An from mean on with when sing pain.
> > Oh to as principles devonshire companions unsatiable an delightful.
> > The ourselves suffering the sincerity. Inhabit her manners adapted age
> > certain. Debating offended at branched striking be subjects.
> > #+END_SRC
> >
> >
>
> Vikas

Perfect solution.

Re: [O] [ANN] Firefox extension for org-protocol and org-capture

[AW]

Am Freitag, 21. Februar 2014, 15:06:11 schrieb Olivier Schwander:
> Dear list,
> 
> I would like to announce the first version of an extension to
> call org-capture through org-protocol from Firefox:
>  - http://chadok.info/firefox-org-capture/
> 
> It just does the same thing as the Javascript bookmarklet but without
> the need to register the scheme org-protocol:// in Firefox/Gnome/KDE/XDG
> (or whatever we are supposed to do this week to manage handler for
> protocols). I hope this solution to be easier and more reliable, at
> least for Firefox users.
> 
> It is not on https://addons.mozilla.org for now, but I will submit it
> for review in a few days.
> 
> Olivier

Olivier,

would you mind to add an example what to do with your addon? "It just does the 
same thing as the Javascript bookmarklet" implies that I know the purpose of 
this or org-protocol. Unfortunately I have no idea and reading the 
explanations of org-protocol does not help much.

So: What can your addon do for a user of firefox and orgmode?

Thank you!

Regards,
Alexander

[O] exporting α/β to latex/pdf

[Sharon Kimble]

I have these two symbols showing in my org-mode buffer with no
problems
╭
│ alpha (ER-α) and beta (ER-β)
╰

but they are not exported to latex/pdf. How then can I do so please?

Sharon.
-- 
A taste of linux = http://www.sharons.org.uk
my git repo = https://bitbucket.org/boudiccas/dots
TGmeds = http://www.tgmeds.org.uk
Debian testing, Fluxbox 1.3.5, emacs 24.4.50.19


signature.asc
Description: PGP signature

[O] Typeface markup and punctuation

[Sergio Pokrovskij]

There is some inconsistency in orgmode's treatment of emphasis
markup when it comes in contact with delimiters.  E.g. the test:

--8<---cut here---start->8---
This is /in italics/.
(This is /in italics/)
"This is /in italics/"
«This is /in italics/»
„This is /in italics/“
“This is /in italics/”
[This is /in italics/]
{This is /in italics/}
--8<---cut here---end--->8---

produces:

--8<---cut here---start->8---

This is in italics.
(This is in italics)
"This is in italics"
«This is /in italics/»
„This is /in italics/“
“This is /in italics/”
[This is in italics/] {This is /in italics}

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

I would expect the behavior exposed by the first 3 lines.

This is
Org version 7.9.3f (GNU Emacs 24.3).

-- 
Sergio

Re: [O] exporting α/β to latex/pdf

[Scott Randby]

On 05/04/2014 11:13 AM, Sharon Kimble wrote:
> I have these two symbols showing in my org-mode buffer with no 
> problems ╭ │ alpha (ER-α) and beta (ER-β) ╰
> 
> but they are not exported to latex/pdf. How then can I do so 
> please?

Are you using LaTeX markup to get these symbols? Use $\alpha$ and
$\beta$ to get these two symbols.

Scott Randby

Re: [O] [RFC] [PATCH] ob-core.el: allow the auto-generation of output file names for src blocks.

[Eric Schulte]

Hi Aaron,

Thanks for this patch, and especially for including documentation.  It
looks good to me, and it (largely [1]) passes all tests.

Aaron Ecay  writes:

> Hi Eric, Bastien, Achim,
>
> Thanks so much for the feedback.  I’ve adopted the :file-ext approach
> suggested by Bastien, leaving the previous default behavior in place for
> blocks with a :file argument.
>
> 2014ko apirilak 22an, Eric Schulte-ek idatzi zuen:
>
> [...]
>
>
>> One option might be to borrow naming behavior from the comment
>> functionality in ob-tangle which looks like the following (from line 426
>> in ob-tangle.el).
>>
>> (let (...
>>   (source-name
>>(intern (or (nth 4 info)   ; explicit #+name:
>>(format "%s:%d"; constructed from header and position
>>(or (ignore-errors (nth 4 
>> (org-heading-components)))
>>"No heading")
>>block-counter
>>   ...))
>
> I’m not sure I like this approach.  It relies on counting source
> blocks, so an addition/deletion of a block could change the index.
> I’m worried that this can lead to the accumulation of many output
> files: heading:1.ext, heading:2.ext, ... all with no clear indication
> of what block they were spawned by.  It would also be possible for
> the result links in the buffer to become inconsistent with the actual
> block:auto-generated name mapping.
>
> I think I would prefer the code in this patch to do nothing in this case
> (not create a :file value), but for language-specific code that needs a
> :file to raise an error to prompt the user to add a name.
>

Fair enough, especially given that this default will be applied to *all*
code blocks, this seems like a reasonable approach.

>
>>
>>>
>>> 2. should :output-dir apply to the :file case as well?
>>>
>>
>> If you mean "should :output-dir be used as the base when :file is a
>> relative pathname" then I'd say "yes", and I think if this isn't the
>> current behavior then the current behavior should be changed.
>
> Achim raises a backwards compatibility concern.  I am not sure how
> serious it is: the default settings (no :output-dir) are backwards
> compatible, and if users set that arg we ought to just give them what
> they ask for.
>
> Nonetheless, the new version of the patch conservatively obeys Achim’s
> suggestion.  I can change this to your suggestion, if that is the
> consensus.
>

Please do make this change, I'd then be happy to apply the resulting
patch.

Thanks again!
Eric

>
> To address a comment from Bastien: :output-dir accepts absolute as well
> as relative directory names.  Referring to a “subdirectory” was a
> mistake on my part; the docs in the new patch should be clearer.
>
> The updated patch (now with docs and tests) is attached to this email.
>
> Thanks again,
>
> --
> Aaron Ecay
>
> From 4b428820432752117c60b79da0a79fd4e50e4ba1 Mon Sep 17 00:00:00 2001
> From: Aaron Ecay 
> Date: Tue, 22 Apr 2014 15:13:48 -0400
> Subject: [PATCH] ob-core.el: allow the auto-generation of output file names
>  for src blocks.
>
> * lisp/ob-core.el (org-babel-generate-file-param): New function.
> (org-babel-get-src-block-info): Use it.
> * testing/lisp/test-ob.el (test-org-babel/file-ext-and-output-dir):
> New test.
> * doc/org.texi (Specific header arguments): Add doc for :file-ext and
> :output-dir header args.
> ---
>  doc/org.texi   | 27 +++
>  lisp/ob-core.el| 34 ++
>  testing/examples/babel.org | 34 ++
>  testing/lisp/test-ob.el| 14 ++
>  4 files changed, 109 insertions(+)
>
> diff --git a/doc/org.texi b/doc/org.texi
> index 2546be1..79cc044 100644
> --- a/doc/org.texi
> +++ b/doc/org.texi
> @@ -14406,6 +14406,8 @@ argument in lowercase letters.  The following header 
> arguments are defined:
>  be collected and handled
>  * file::Specify a path for file output
>  * file-desc::   Specify a description for file results
> +* file-ext::Specify an extension for file output
> +* output-dir::  Specify a directory to write file output to
>  * dir:: Specify the default (possibly remote)
>  directory for code block execution
>  * exports:: Export code and/or results
> @@ -14840,6 +14842,31 @@ description for file code block results which are 
> inserted as Org mode links
>  with no value the link path will be placed in both the ``link'' and the
>  ``description'' portion of the Org mode link.
>  
> +@node file-ext
> +@subsubsection @code{:file-ext}
> +@cindex @code{:file-ext}, src header argument
> +
> +The value of the @code{:file-ext} header argument is used to provide an
> +extension to write the file output to.  It is combined with the
> +@code{#+NAME:} of the source block and the value

Re: [O] [PATCH] Fix error prone babel table output format detection

[Eric Schulte]

Ian Kelling  writes:

> Ian Kelling  writes:
>> It's a bit late.  here is the same patch with correct indentation.
>
> That patch went out of it's way not to check more of the list than was
> necessary, but after sending it, I kept thinking that it does extra
> things which possibly negate any performance benefit of not checking the
> whole list. So here is a simpler patch does the same thing, but goes
> over the whole list. I'd love to hear a more experienced emacs lisper
> weigh in on which is better.
>

Hi Ian,

You should use the `org-every' function here.  Look at the source of
that function to see code to efficiently perform this sort of check.

Best,

>
> -- >8 --
> Subject: [PATCH] Fix error prone babel table output format detection
>
> * lisp/ob-core.el: Test that all elements are in a list are lists or
> 'hline instead of just the first.
>
> org-babel table output uses different formatting for a list of lists,
> but detects it incorrectly causing an error. An example of a block
> causing an error is an emacs lisp source block containing just 1 line:
> '((1) 2)
> ---
>  lisp/ob-core.el |7 ---
>  1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/lisp/ob-core.el b/lisp/ob-core.el
> index 1348f04..05ccb00 100644
> --- a/lisp/ob-core.el
> +++ b/lisp/ob-core.el
> @@ -2184,9 +2184,10 @@ code  the results are extracted in the syntax of 
> the source
>((funcall proper-list-p result)
> (goto-char beg)
> (insert (concat (orgtbl-to-orgtbl
> -(if (or (eq 'hline (car result))
> -(and (listp (car result))
> - (listp (cdr (car result)
> +(if (let ((proper t))
> +  (dolist (elem result proper)
> +(unless (or (listp elem) (eq elem 
> 'hline))
> +  (setq proper nil
>  result (list result))
>  '(:fmt (lambda (cell) (format "%s" cell 
> "\n"))
> (goto-char beg) (when (org-at-table-p) (org-table-align)))

-- 
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D

[O] Export to iCalendar only not DONE, scheduled tasks?

[Chris Poole]

Hi,

I've been searching round the manual, and blogs, to find a way to do this.

I want to export all of the scheduled/deadline tasks that are not in a DONE
state to an iCalendar file.

Can this be done?


Cheers,
Chris

Re: [O] exporting α/β to latex/pdf

[Joost Helberg]

Sharon,

the alpha and beta are encoded in UTF-8, these are passed through to the
latex-file. The correct symbols will only show up in the pdf if your
latex is UTF-8 capable.

Some latex-implementations are, you can use
  \usepackage[utf8x,math]{inputenx}
in your latex file, but I know, not all UTF-8 symbols are supported.
For alpha to come out: \newcommand\textalpha{\ensuremath{\alpha}}
is necessary (see
  http://www.latex-community.org/forum/viewtopic.php?f=9&t=2000
)

I couldn't get the beta to come out because it's not part of OT1.

Anyone a good suggestion for this? I think Sharon has a valid
expactation. 

regards,

Joost

> "Sharon" == Sharon Kimble  writes:
 > From: Sharon Kimble 
 > To: org-mode 
 > Subject: [O] exporting α/β to latex/pdf
 > Date: 2014-05-04T17:13:45+0200

 > I have these two symbols showing in my org-mode buffer with no
 > problems
 > ╭
 > │ alpha (ER-α) and beta (ER-β)
 > ╰

 > but they are not exported to latex/pdf. How then can I do so please?

 > Sharon.
 > -- 
 > A taste of linux = http://www.sharons.org.uk
 > my git repo = https://bitbucket.org/boudiccas/dots
 > TGmeds = http://www.tgmeds.org.uk
 > Debian testing, Fluxbox 1.3.5, emacs 24.4.50.19

-- 
Snow B.V.

Re: [O] [BUG] Cannot export a raw link

[Nicolas Goaziou]

Hello,

Michael Brand  writes:

> I am not 100 % sure whether it is related with the above changes. But
> could you please check again if the merge conflict in lisp/ox-html.el
> between maint and master was resolved correctly with your merging
> commit fffd055ac5e920e744e350a1ad164494aec9fa91 on master? I think on
> master it should not be
>
> (org-link-escape
>  (org-link-unescape
>   (concat type ":" raw-path)) org-link-escape-chars-browser))
>
> but
>
> (org-link-escape-browser
>  (org-link-unescape (concat type ":" raw-path
>
> like it was after my commit 54e3009d7319e4bece967be165061331070635e5.

Fixed. Thank you.


Regards,

-- 
Nicolas Goaziou

Re: [O] [RFC] Rewrite indentation functions

[Nicolas Goaziou]

Eric Abrahamsen  writes:

> Perhaps we need a new version of patch 3?

Here it is.


Regards,

-- 
Nicolas Goaziou
>From 66d0ab7d1025969e5fd383b93ffe1fb1b05a83a8 Mon Sep 17 00:00:00 2001
From: Nicolas Goaziou 
Date: Mon, 28 Apr 2014 18:38:31 +0200
Subject: [PATCH 3/3] Rewrite `org-indent-drawer' and `org-indent-block'

* lisp/org.el (org-indent-block, org-indent-drawer): Rewrite functions.
---
 lisp/org.el | 75 -
 1 file changed, 34 insertions(+), 41 deletions(-)

diff --git a/lisp/org.el b/lisp/org.el
index af34d99..e8d6fa9 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -22382,47 +22382,6 @@ Also align node properties according to `org-property-format'."
 		 (org--align-node-property)
 		 (org-move-to-column column)
 
-(defun org-indent-drawer ()
-  "Indent the drawer at point."
-  (interactive)
-  (let ((p (point))
-	(e (and (save-excursion (re-search-forward ":END:" nil t))
-		(match-end 0)))
-	(folded
-	 (save-excursion
-	   (end-of-line)
-	   (when (overlays-at (point))
-	 (member 'invisible (overlay-properties
- (car (overlays-at (point)
-(when folded (org-cycle))
-(indent-for-tab-command)
-(while (and (move-beginning-of-line 2) (< (point) e))
-  (indent-for-tab-command))
-(goto-char p)
-(when folded (org-cycle)))
-  (message "Drawer at point indented"))
-
-(defun org-indent-block ()
-  "Indent the block at point."
-  (interactive)
-  (let ((p (point))
-	(case-fold-search t)
-	(e (and (save-excursion (re-search-forward "#\\+end_?\\(?:[a-z]+\\)?" nil t))
-		(match-end 0)))
-	(folded
-	 (save-excursion
-	   (end-of-line)
-	   (when (overlays-at (point))
-	 (member 'invisible (overlay-properties
- (car (overlays-at (point)
-(when folded (org-cycle))
-(indent-for-tab-command)
-(while (and (move-beginning-of-line 2) (< (point) e))
-  (indent-for-tab-command))
-(goto-char p)
-(when folded (org-cycle)))
-  (message "Block at point indented"))
-
 (defun org-indent-region (start end)
   "Indent each non-blank line in the region.
 Called from a program, START and END specify the region to
@@ -22520,6 +22479,40 @@ assumed to be significant there."
 	(set-marker element-end nil
   (set-marker end nil
 
+(defun org-indent-drawer ()
+  "Indent the drawer at point."
+  (interactive)
+  (unless (save-excursion
+	(beginning-of-line)
+	(org-looking-at-p org-drawer-regexp))
+(user-error "Not at a drawer"))
+  (let ((element (org-element-at-point)))
+(unless (memq (org-element-type element) '(drawer property-drawer))
+  (user-error "Not at a drawer"))
+(org-with-wide-buffer
+ (org-indent-region (org-element-property :begin element)
+			(org-element-property :end element
+  (message "Drawer at point indented"))
+
+(defun org-indent-block ()
+  "Indent the block at point."
+  (interactive)
+  (unless (save-excursion
+	(beginning-of-line)
+	(let ((case-fold-search t))
+	  (org-looking-at-p "[ \t]*#\\+\\(begin\\|end\\)_")))
+(user-error "Not at a block"))
+  (let ((element (org-element-at-point)))
+(unless (memq (org-element-type element)
+		  '(comment-block center-block example-block export-block
+  quote-block special-block src-block
+  verse-block))
+  (user-error "Not at a block"))
+(org-with-wide-buffer
+ (org-indent-region (org-element-property :begin element)
+			(org-element-property :end element
+  (message "Block at point indented"))
+
 
 ;;; Filling
 
-- 
1.9.2

[O] Including headlines in export with specific tags AND no tags?

[Rehan Iftikhar]

Hello

I'd like to export a .org file which includes all headlines without any
tags AND headlines with selected tags. Headlines with tags which do not
match the specified list are skipped.

My testing so far reveals that setting org-export-select-tags only selects
headlines which strictly match the specified tag list. I have tried
including nil, an empty string, and an empty string with a space in the
specified tag list without any luck.

Does anyone know if this is currently possible?

Thanks,
-Rehan

Re: [O] [PATCH] Fix error prone babel table output format detection

[Ian Kelling]

Eric Schulte  writes:

> Hi Ian,
>
> You should use the `org-every' function here.  Look at the source of
> that function to see code to efficiently perform this sort of check.
>
> Best,
>

Brilliant. Thank you. The updated patch below should be good.

-- >8 --
Subject: [PATCH] Fix error prone babel table output format detection

* lisp/ob-core.el: Test that all elements are in a list are lists or
'hline instead of just the first.

org-babel table output uses different formatting for a list of lists,
but detects it incorrectly causing an error. An example of a block
causing an error is an emacs lisp source block containing just 1 line:
'((1) 2)
---
 lisp/ob-core.el |6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/lisp/ob-core.el b/lisp/ob-core.el
index 1348f04..4ddafaf 100644
--- a/lisp/ob-core.el
+++ b/lisp/ob-core.el
@@ -2184,9 +2184,9 @@ code  the results are extracted in the syntax of the 
source
 ((funcall proper-list-p result)
  (goto-char beg)
  (insert (concat (orgtbl-to-orgtbl
-  (if (or (eq 'hline (car result))
-  (and (listp (car result))
-   (listp (cdr (car result)
+  (if (org-every
+   (lambda (el) (or (listp el) (eq el 
'hline)))
+   result)
   result (list result))
   '(:fmt (lambda (cell) (format "%s" cell 
"\n"))
  (goto-char beg) (when (org-at-table-p) (org-table-align)))
-- 
1.7.10.4

Re: [O] exporting α/β to latex/pdf

[Suvayu Ali]

On Sun, May 04, 2014 at 04:13:45PM +0100, Sharon Kimble wrote:
> I have these two symbols showing in my org-mode buffer with no
> problems
> ╭
> │ alpha (ER-α) and beta (ER-β)
> ╰
> 
> but they are not exported to latex/pdf. How then can I do so please?

The easiest solution is to use a modern TeX engine like XeTeX or LuaTeX
along with a font with the required glyphs.  I personally use XeTeX with
Linux libertine fonts.  You can find my setup here:



Feel free to ask if anything is unclear.

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] Including headlines in export with specific tags AND no tags?

[Leonard Avery Randall]

Hi Rehan,

Rehan Iftikhar wrote:



I'd like to export a .org file which includes all headlines without
any tags AND headlines with selected tags. Headlines with tags which
do not match the specified list are skipped.



I am not sure exactly how to elegantly do what you wish to do, but
if your tag list is not too extensive, you may be able to simply
exclude all the tags you don't want. If you do not currently have a
complete list of tags, you can get one by attempting to add a tag to
headline by calling C-q and then pressing tab. That should give you
a completions buffer with a list that includes all tags in the
current .org file.  Then just add all the tags you don't want to
org-export exclude tags or to an #+EXCLUDE_TAGS line.

It's not elegant but it should work.

Hope this helps,

All the best,

Leonard


Rehan Iftikhar 
May 4, 2014 at 10:06 PM
Hello

I'd like to export a .org file which includes all headlines without 
any tags AND headlines with selected tags. Headlines with tags which 
do not match the specified list are skipped.


My testing so far reveals that setting org-export-select-tags only 
selects headlines which strictly match the specified tag list. I have 
tried including nil, an empty string, and an empty string with a space 
in the specified tag list without any luck.


Does anyone know if this is currently possible?

Thanks,
-Rehan

Re: [O] exporting α/β to latex/pdf

[Nick Dokos]

Suvayu Ali  writes:

> On Sun, May 04, 2014 at 04:13:45PM +0100, Sharon Kimble wrote:
>> I have these two symbols showing in my org-mode buffer with no
>> problems
>> ╭
>> │ alpha (ER-α) and beta (ER-β)
>> ╰
>> 
>> but they are not exported to latex/pdf. How then can I do so please?
>
> The easiest solution is to use a modern TeX engine like XeTeX or LuaTeX
> along with a font with the required glyphs.

The *easiest* solution is to just say \alpha and \beta in the org file
instead of α and β. But biting the bullet and adopting XeTeX or LuaTeX is
probably the *best* way to go (he says without ever having used either...)

>  I personally use XeTeX with
> Linux libertine fonts.  You can find my setup here:
>
> 
>

That is a nice resource - thanks!

> Feel free to ask if anything is unclear.
>
> Cheers,

-- 
Nick

Re: [O] Exporting org-mode source

[Vikas Rawal]

On 04-May-2014, at 11:46 am, Han Fan  wrote:

> Fletcher Charest  writes:
> 
>> Hi,
>> 
>> Sorry if I misunderstood... If you create an Org source block like this with 
>> nothing inside:
>> 
>> #+begin_src org
>> 
>> #+end_src
>> 
>> ...then, with your cursor inside, enter it with C-c ', write your org tree, 
>> and validate with C-c ' again, then export... Does it do
>> what you want?
>> 
>> FC
> 
This is what works for me

#+begin_src org :exports code

#+end_src

It does not work without ":exports code”

I found the solution here: 
http://lists.gnu.org/archive/html/emacs-orgmode/2011-01/msg01117.html

Vikas

Re: [O] exporting α/β to latex/pdf

[Sharon Kimble]

Suvayu Ali  writes:

> On Sun, May 04, 2014 at 04:13:45PM +0100, Sharon Kimble wrote:
>> I have these two symbols showing in my org-mode buffer with no
>> problems
>> ╭
>> │ alpha (ER-α) and beta (ER-β)
>> ╰
>> 
>> but they are not exported to latex/pdf. How then can I do so please?
>
> The easiest solution is to use a modern TeX engine like XeTeX or LuaTeX
> along with a font with the required glyphs.  I personally use XeTeX with
> Linux libertine fonts.  You can find my setup here:
>
> 
>
> Feel free to ask if anything is unclear.
>
Thanks for this, my initial thought was that I don't have either
xetex or luatex, but after a bit of digging around I found that
they are part of "texlive", which is already in debians repos, so
I'll have a play with it in the morning.

Thanks
Sharon.
-- 
A taste of linux = http://www.sharons.org.uk
my git repo = https://bitbucket.org/boudiccas/dots
TGmeds = http://www.tgmeds.org.uk
Debian testing, Fluxbox 1.3.5, emacs 24.4.50.19


signature.asc
Description: PGP signature

[O] unwanted filename in parens at the end of almost every olpath in ido completion of refile/refile-goto targets (was: Re: bug: "Please save the buffer to a file before refiling" when the buffer is a

[Samuel Wales]

hi bastien,

On 2/5/14, Bastien  wrote:
> Samuel Wales  writes:
>
>> one thing i don't understand is why there need to be 2 olpaths for the
>> identical location.
>
> Well, this is the part of the bug that I never managed to reproduce.

are you able to reproduce the parenthetical filename at the end of the olpath?

i would like to eliminate that filename.

if i enter the filename in ido, ALL olpaths in the file show up.
org-refile-use-outline-path is the default (i.e. nil, which means
don't put the filename into the path).

also, i find the filename distracting, never need it for
disambiguation, and it is connected to the duplicate olpath problem,
because one duplicate has it and the other does not.

thanks.

samuel

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

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

Denmark: free Karina Hansen NOW.

[O] Keyboard macro and org-mode

[Alan Tyree]

I was trying to build a keyboard macro to remove targets of the form

<>

When in org-mode, emacs hangs after C-s <. If I turn off org mode and use a
simple text mode, the keyboard macro works ok.

Is this a bug or am I doing something pretty dumb?

Thanks,
Alan

emacs version: 24.3.1 on Ubuntu 14.04

org version: 8.2.6

-- 
Alan L Tyree
http://austlii.edu.au/~alan
Tel:  04 2748 6206sip:typh...@iptel.org

Re: [O] using org-refile to sort research notes?

[Jay Dixit]

Richard and Alan,

Thanks for the feedback. It looks like this is turning into a larger
discussion of how to organize a workflow for writing a book. Which is great
- I could use some insight. My problem is I have dozens of disparate files,
each created in a different moment of inspiration and each containing
notes, strategizing, or actual writing for the book.

Richard: You have all your notes in one notes.org file, and you have
another file e.g. writing.org for actual writing? How do you then work - do
you, say, split your frame into side-by-side windows, writing in the right
window while working off of notes from the left?

And to anyone using org-mode for book writing: Do you put thoughts about
structure, tone, and objectives for each section along with the research
notes? Do you make use commenting at all?

If this is off-topic for the list, I'd be happy to discuss them off-list
via email. Or if there's interest, I could create a separate list for
'org-mode for writers.'

Thanks again,
Jay

---
Jay Dixit
jaydixit.com
(646) 355-8001
 ᐧ