Re: [O] [PATCH] No title in org-export-as-odt

2014-03-28 Thread Brady Trainor
Bastien bzg at gnu.org writes:

 Brady Trainor algebrat at uw.edu writes:
 
  For my solution, I changed insert to ignore. 
 
 Can you provide your change in the form of a patch?
 

 4. in Emacs, hit `C-x v =' from the file to create the patch


I wanted to return to this and attempt it, here is my first patch ever: 


diff --git a/lisp/ox-odt.el b/lisp/ox-odt.el
index da2ca3f..8c7f0fe 100644
--- a/lisp/ox-odt.el
+++ b/lisp/ox-odt.el
@@ -1491,7 +1491,7 @@ original parsed data.  INFO is a plist holding export 
options.
   (goto-char (match-beginning 0))

   ;; Preamble - Title, Author, Date etc.
-  (insert
+  (ignore
(let* ((title (org-export-data (plist-get info :title) info))
   (author (and (plist-get info :with-author)
(let ((auth (plist-get info :author)))


I installed a fresh version of org-mode from Elpa or Melpa before doing 
this. (I am just now looking a little into the maint branch.)

In the long-long run, when I go to insert the code, I wonder why we don't 
make removing the title an option in ox.el. Otherwise, I might've 
considered figuring out how to expose the above ad-hoc solution as a 
variable in the customize group. I don't know what the use cases are for 
the title. So, a temporary solution might go, org-odt-export-preamble off 
and on.

(ETA: then, perhaps the individual exporters should be focused on, before 
considering pulling variables back to ox.el.) 

Thank you always for org-mode,

Brady

P.S., so... I went ahead and tried the exposed variable fix, and that is 
below: (This was my first shot at making a Emacs customizable variable, 
blindly with no RTFM, and... I don't think it works as is.) 

diff --git a/lisp/ox-odt.el b/lisp/ox-odt.el
index da2ca3f..c2b4609 100644
--- a/lisp/ox-odt.el
+++ b/lisp/ox-odt.el
@@ -351,6 +351,16 @@ the entity.  See `org-odt--enumerate'.)
   :group 'org-export)


+ Insert Preamble (Title, Author...)
+
+(defcustom org-odt-insert-preamble 'nil
+  Choose whether title and author preamble appears in export.
+  :group 'org-export-odt
+  :version 24.1
+  :type 'boolean
+  )
+
+
  Debugging

 (defcustom org-odt-prettify-xml nil
@@ -1491,6 +1501,7 @@ original parsed data.  INFO is a plist holding export 
options.
   (goto-char (match-beginning 0))

   ;; Preamble - Title, Author, Date etc.
+  (if org-odt-insert-preamble
   (insert
(let* ((title (org-export-data (plist-get info :title) info))
   (author (and (plist-get info :with-author)
@@ -1543,7 +1554,7 @@ original parsed data.  INFO is a plist holding export 
options.
(org-odt--format-timestamp (car date))
  (org-export-data (plist-get info :date) info)))
;; Separator
-   text:p text:style-name=\OrgSubtitle\/))
+   text:p text:style-name=\OrgSubtitle\/)))
   ;; Table of Contents
   (let* ((with-toc (plist-get info :with-toc))
  (depth (and with-toc (if (wholenump with-toc)







Re: [O] [Patch] Few small fixes to html header

2014-03-28 Thread Rainer M Krug
Marcin Antczak marcin.antc...@neutrico-themes.pl writes:

 I've attached patch below, but I'm affraid that there is something wrong
 with indentation.
 I'm not sure if there is problem with my settings or just entire
 ox-html.el is indented badly.

 I've been trying to indent file with the default parameters.
 I started Emacs with -Q parameter and as I can see there is
 a .dir-locals.el in org-mode repo.

 So, everything should be ok. Unfortunately there are some differences related 
 to indentation in my patch.

 Please review and accept this patch, or enlighten me how to set
 indentation properly.


 My patch fixes HTML meta data produced on export by ox-html.el

 1. Meta charset definition should be set before title as document title can 
 contain
 some unicode symbols etc.

 2. Added viewport declaration as described here:

 https://github.com/h5bp/html5-boilerplate/blob/v4.3.0/doc/html.md

 here:

 https://developer.apple.com/library/safari/documentation/AppleApplications/Reference/SafariWebContent/UsingtheViewport/UsingtheViewport.html

 3. Fixed unnecessary \n at the end of Description meta.
 4. Removed unnecessary spaces in meta tags.



 Marcin



-- 
Rainer M. Krug
email: Raineratkrugsdotde
PGP: 0x0F52F982


smime.p7s
Description: S/MIME cryptographic signature


[O] How to setup this custom function with Org-mode functions? (org-habit)

2014-03-28 Thread stardiviner

I want to create a custom keybinding to custom function which will execute all
necessary steps for creating an org habit.
The bellowing is my code, but seems it doesn't work at all.
I don't know how to write this custom function actually. (I just put some 
keybindings
corresponding functions in the custom function body.) And some org-mode
functions are interactively.

#+BEGIN_SRC emacs-lisp
;; TODO: create an key binding for all necessary steps for create a habit. 
(reference in Org-mode.org file)
(defun org-habit-apply ()
  Apply org-habit on this task.
  (interactive)
  (lambda ()
(org-todo HABIT)
(org-insert-property-drawer); TODO: :STYLE: habit (value)
(org-schedule)))

(define-key org-mode-map (kbd C-c C-x h) 'org-habit-apply)
#+END_SRC

Does anybody can help me this? and thanks in advance.

-- 
[ stardiviner ] I want to save myself from this world.
IRC(freenode): stardiviner \ Google+:  numbchild \
http://about.me/Evanescence/




Re: [O] [PATCH] Add catch-up all LaTeX errors

2014-03-28 Thread Francesco Pizzolante
Hi Marcin,

 This is rather a workaround, but don't use Adobe Reader, use any other
 PDF viewer instead.  (IIRC, there's also a workaround that makes Adobe
 Reader behave correctly, i.e. not lock the pdf file, but I can't find
 it now.  See here, for example:
 http://stackoverflow.com/questions/4910029/possible-to-make-adobe-reader-not-hold-a-file-lock-on-windows)
 (I, for one, did welcome our new Linux overlords more than a decade
 ago, and don't experience that problem at all, using first xpdf, and
 now evince.;))

Thanks for your reply and your suggestion.

I already use SumatraPDF (as suggested in your link) since a long time
now to avoid this locking problem and it works very well.

I'm taking this locking issue as an example to show that some errors are
not catched up when we export to LaTeX.

Best Regards,
 Francesco



Re: [O] Space in Exported Text

2014-03-28 Thread Marcin Borkowski
Dnia 2014-03-26, o godz. 14:56:08
Ken Mankoff mank...@gmail.com napisał(a):

 
 On 2014-03-26 at 14:32, Esben Stien wrote:
  If I f.ex make a beautiful table in org-mode: 
 
  |-+-+---++-|
  | foo | bar | xyzzy | hukarz | |
  | qux | | corge | grault | garply waldo fred plugh |
  | baz | |   || |
  |-+-+---++-|
 
   , it's not so beautiful anymore if I send it in an email.
 
  Is it not possible to force these spacings as space?
 
  I guess this is gnus fault, but I'm not really sure.
 
 Looks perfect to me. I'm using fixed-width font in my email
 client. Changing tabs to spaces won't solve bad looking tables because
 most people use variable-width fonts. Nothing you can do about that.

Terrible choice: HTML emails are evil.  Monospace fonts are illegal.

https://twitter.com/xor/status/432710872117428224

New evidence suggests that Manning, Snowden, and Assange each used a
powerful tool called monospace fonts.  Unlike the fonts innocent
Americans are familiar with, the 'monospace' fonts preferred by hackers
are most associated with cybercrime.

:)

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



[O] TODOs and birthdays

2014-03-28 Thread Sharon Kimble
I have a document called 'organiser.org' which is mainly comprised of various
TODOs under various projects, and various NEXT under birthdays and hospital
appointments. These TODOs can be up to 4 levels in depth, and with one level 1
TODO as the project header. How can all of these TODOs be included in the agenda
please?

And for the birthday TODOs, how can I include the date of birth so that it shows
their age please? Like - 
,
| *** TODO Winnie Poohs birthday - is 83
| SCHEDULED: 2014-12-02 Tue AGE: 1930-12-02
`

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.3.1


pgp0kEOUoqKwd.pgp
Description: PGP signature


Re: [O] [BABEL] BUG Re: Omitting try/catch blocks from tangled R code?

2014-03-28 Thread Rainer M Krug


bini55Rmu2tZs.bin
Description: application/pgp-encrypted


binZzbsrmcnDw.bin
Description: Binary data


Re: [O] [BABEL] BUG Re: Omitting try/catch blocks from tangled R code?

2014-03-28 Thread Rainer M Krug
Eric Schulte schulte.e...@gmail.com writes:

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

 Eric Schulte schulte.e...@gmail.com writes:

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

 Eric Schulte schulte.e...@gmail.com writes:

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

 Eric Schulte schulte.e...@gmail.com writes:

 Charles Berry ccbe...@ucsd.edu writes:

 John Hendy jw.hendy at gmail.com writes:

 [deleted]
 
  I think the default behavior should be reverted, as tangling and
  exporting are two different things. When I tangle, I want to see the
  code blocks as they are in the org document (with possible 
  variables and
  expansions) but not to create files where I do not put it explicitly
  into a code block. These wrappers have nothing to do with the code, 
  and
  are only there for the exported engine. So I would either revert to 
  the
  original behavior, or, introduce a new header argument,
  e.g. :include-wrappers, which would, if set to t, include the export
  wrappers in the tangled file. This might be useful for debugging
  exporting of code block results, but not for general tangling.
 
 Thanks for chiming in. This was my gut reaction to the default
 behavior. I guess we're still only a sample size of 2, but
 intuitively, I would think that tangling would be a separate beast in
 most cases from exporting. Just to have it on the record, if I tangle,
 it's usually to take the code I've used in something like a Beamer
 presentation or document and combine it into a single .R file so
 someone can run it without needing Org-mode.

 [deleted]

 Sorry to be late to add my $0.02...

 I never want the try/catch wrappers.

 But noweb is indispensable.

 I use noweb a lot to organize and collect blocks. In some cases, I 
 export
 them and in others I just tangle them.

 I hope that the revised code will allow me to turn off try/catch 
 wrapping
 and still be able to use noweb when tangling or exporting.


 In addition to noweb, there are cases where variable expansion is useful
 in tangled code.

 The simplest option is to move things like try/catch blocks out of the
 code block expansion function, and into the execution function.  Then if
 other language present similar constructs (which we want to add to
 execution by default but never want to tangle), we can think about
 abstracting this out into some new level of code block expansion.

 Thoughts?

 Makes perfect sense to me, and would definitely be the better place to
 add them.

 If one wants enclosing code in the tangling, there is always
 the :epilogue and :prologue header arguments, and the try/catch should
 be considered as internal to the execution.


 Great, how's this patch work?  If it looks good I'll apply it.

 Git still puzzles me a lot... If you tell me how I can apply this patch
 (from emacs?) I will try it out.


 Here are some instructions from the command line.

 1. write the patch out to a file on disk, say /tmp/0001-etc...patch

 2. cd into the org-mode directory

 3. make sure you're up to date with the latest

  git pull

 4. apply the patch

  git am /tmp/0001-etc...patch

 and that should do it.

 OK - managed to apply the patch.

 Using 

 Org-mode version 8.2.5h (release_8.2.5h-846-geb806d @ 
 /Users/rainerkrug/.emacs.d/org-mode/lisp/)

 updated this morning, I get the following error:


 Could you provide a minimal example file generating this error?

Apologies - I am still struggling with encryption..

So here is my example:

--8---cut here---start-8---
#+TITLE: single_to_multi
#+DATE: 2013-10-15 Tue
#+AUTHOR: Rainer M. Krug
#+EMAIL: rai...@krugs.de

≈* Load R packages and data
#+BEGIN_SRC R
cat(Loading Data\n)
#+END_SRC
--8---cut here---end---8---

I am using only org loaded and R enabled.

C-c C-c on the block produces the error

emacs version: 
GNU Emacs 24.3.1 (x86_64-apple-darwin13.0.0, Carbon Version 1.6.0
AppKit 1265) of 2014-02-13 on Rainers-MacBook-Pro-2.local

org version:
Org-mode version 8.2.5h (release_8.2.5h-837-gb296cc @
/Users/rainerkrug/.emacs.d/org-mode/lisp/)

Cheers,

Rainer


 Thanks,


 ,
 | Debugger entered--Lisp error: (wrong-type-argument sequencep 67)
 |   mapconcat(identity COLUMNS -
 | 
 read.table(\/var/folders/50/wcr5bjwn75q595n6x82gxj28gn/T/babel-21363l1U/R-import-21363S9b\,\n
 | header=TRUE,\n row.names=1,\n sep=\\\t\,\n
 | as.is=TRUE)\nCOLS_TO_EVAL -
 | 
 read.table(\/var/folders/50/wcr5bjwn75q595n6x82gxj28gn/T/babel-21363l1U/R-import-21363fHi\,\n
 | header=TRUE,\n row.names=1,\n sep=\\\t\,\n as.is=TRUE)\nALLSPECIES
 | -
 | 
 read.table(\/var/folders/50/wcr5bjwn75q595n6x82gxj28gn/T/babel-21363l1U/R-import-21363sRo\,\n
 | header=TRUE,\n row.names=1,\n sep=\\\t\,\n as.is=TRUE)\nSPECIES -
 | 
 read.table(\/var/folders/50/wcr5bjwn75q595n6x82gxj28gn/T/babel-21363l1U/R-import-213635bu\,\n
 | header=TRUE,\n row.names=1,\n sep=\\\t\,\n as.is=TRUE)\nYEARS -
 | 
 

Re: [O] No title in org-export-as-odt

2014-03-28 Thread Nicolas Goaziou
Hello,

Miguel Ruiz rbeni...@yahoo.es writes:

 If I try

 #+TITLE:

This should remove the title line. Thank you for reporting it.


Regards,

-- 
Nicolas Goaziou



Re: [O] [RFC] Sloppy `org-element-context'?

2014-03-28 Thread Nicolas Goaziou
Hello,

Rasmus ras...@gmx.us writes:

 Would it make sense to make it optional?

I thought about it. But adding an optional argument to determine if
`org-element-context' should be strict or sloppy doesn't help in
practice, since one will probably often wonder if he needs to switch to
sloppy mode or not.

Also, `org-element-context' is not needed for parsing a buffer (with
`org-element-parse-buffer'). Thus, strict behaviour is not mandatory.

 I haven't seen this discussion.  I looked briefly at the suggested
 patch; I don't understand why it would be necessary or desirable.  But
 I will not rule out that I have yet to consider the correct case!

For example, one may write

  :PROPERTIES:
  :SOME_LINK: [[my-link:destination]]
  :END:

and expect C-c C-o to open the link in the properties drawer. I can see
the practical use, but not at the syntax level, which defines it as
a plain string. Indeed, this can get worse:

  :PROPERTIES:
  :REMEMBER: 2014-03-28 Fri
  :END:

introduces a timestamp hidden to the user but not to the agenda.

 As a hacker (not quite a developer!), I do at time desire more
 flexibility with org-context to temporarily evaluating an element
 under alternative assumptions of its properties.  A recent example
 evaluate $x^{z}$ as-if it isn't a latex-fragment.

I think this would go too far. Considering $x^{z}$ as anything else than
a latex fragment is not a good idea. What is the next step? Should the
snippet $a =b \qquad c= d$ be seen as strike-through?


Regards,

-- 
Nicolas Goaziou



Re: [O] Tasks with lots of logbook entries are very slow

2014-03-28 Thread Pere Quintana Seguí
El 26/03/14 09:31, Peter Neilson ha escrit:
 On Wed, 26 Mar 2014 04:10:02 -0400, Pere Quintana Seguí
 p...@quintanasegui.com wrote:
 
 El 25/03/14 19:27, Marcin Borkowski ha escrit:
 Dnia 2014-03-25, o godz. 16:00:01
 Pere Quintana Seguí p...@quintanasegui.com napisał(a):

 I log most of my work with org-mode. Some of my tasks are repetitive,
 this is, I do them weekly or daily (i.e. empty mail inbox). After many
 years, the logs are very long. As a consequence, marking these tasks
 as done is *very* slow.

 Is there a workaround that does not involver deleting the logs?

 Archiving?


 No, archiving would'nt work, as I need the task every day.

 Thanks for the tip.

 Pere
 
 Perhaps this will help:
 
 Standard method for log maintenance outside of org is to rotate logs
 into archive. The current log is only for the current day (or month,
 week, or year). Other criteria, such as log size, can be used to trigger
 rotation. Rotation cuts off the current log, archives it, possibly
 deletes truly ancient logs, and starts a new current log. Look up the
 Linux logrotate command for further info. Here's one description:
 http://www.thegeekstuff.com/2010/07/logrotate-examples/
 
 


I didn't understand your message. I thought you meant archiving the
task, but in fact you meant archiving the logs. That's what I've done.

thanks :-)




Re: [O] Tasks with lots of logbook entries are very slow

2014-03-28 Thread Pere Quintana Seguí
El 26/03/14 09:12, Pere Quintana Seguí ha escrit:
 El 25/03/14 19:47, Achim Gratz ha escrit:
 I've long resorted to using two drawers back-to-back:
 
 That seems to be the most straightforward solution. I'll do that.
 
 Maybe org-mode could do this automatically. A variable would determine
 when log entries should be archived in the second drawer.
 
 I would write a patch if I could program in elisp, but I can't. :'(
 
 Thanks,
 
 Pere

The solution has been configuring org-drawers to create a new drawer
called :LOGBOOKARCHIVE I will put the old logs there, as Achim Gratza
suggested.

Thanks for your tips,

Pere





Re: [O] [Patch] Few small fixes to html header

2014-03-28 Thread Marcin Antczak

Rainer M Krug writes:

 Marcin Antczak marcin.antc...@neutrico-themes.pl writes:

[...]

Is your response intentionally empty or am I missing something?


Marcin



Re: [O] Unconditionally turn off Flyspell mode during export

2014-03-28 Thread Sebastien Vauban
Hello Nick and Bastien,

Nick Dokos wrote:
 Sebastien Vauban writes:

 I use Flyspell in all my text-mode and prog-mode buffers, hence as well
 in my Org mode buffers -- as they ultimately derive from Text mode.

 Though, as you can see, that has the perverse impact that Flyspell gets
 called (even multiple times) during the export process, when creating
 copies of the source Org document:

 Turning on Flyspell in buffer `ecm.txt2'
 Turning on Flyspell in buffer `ecm.txt22'
 Turning on Flyspell in buffer ` *temp*'
 Turning on Flyspell in buffer `ecm.html'
 Saving file d:/ecm.html...
 Wrote d:/ecm.html

 Is it possible to *automatically disable Flyspell during the export*
 *process*, as it's completely useless (the export buffers are killed when
 the export is done) and eats useful CPU cycles?

 Advise org-export-as with an `around' piece of advice where you set the
 text-mode-hook to nil (or just delete the flyspell part) perhaps?

The code:

--8---cut here---start-8---
  (add-hook 'text-mode-hook
(lambda ()
  (message Turning on Flyspell in buffer `%s' (buffer-name))
  (flyspell-mode 1)))

  (defadvice org-export-as (around my-org-export-as activate)
Turn off Flyspell (and other things) when exporting current Org buffer.
(let (text-mode-hook)
  ad-do-it))
--8---cut here---end---8---

 Untested.

Better...

--8---cut here---start-8---
Turning on Flyspell in buffer `ecm.txt'
Turning on Flyspell in buffer `ecm.html'
--8---cut here---end---8---

Still, the HTML [1] exported file is entirely Flyspell'ed...

Best regards,
  Seb

[1] HTML mode derives from Text mode.

-- 
Sebastien Vauban




Re: [O] [PATCH] Add catch-up all LaTeX errors

2014-03-28 Thread Nicolas Goaziou


Hello,

Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org
writes:

 Isn't `orgfile' equal to `org-babel-exp-reference-buffer' in
 `org-latex-compile'?

No, `org-babel-exp-reference-buffer' is a temporary buffer attached to
no file. It cannot help to find original file.


Regards,

-- 
Nicolas Goaziou




Re: [O] TODOs and birthdays

2014-03-28 Thread Ian Barton

On 28/03/14 08:19, Sharon Kimble wrote:



And for the birthday TODOs, how can I include the date of birth so that it shows
their age please? Like -
,
| *** TODO Winnie Poohs birthday - is 83
| SCHEDULED: 2014-12-02 Tue AGE: 1930-12-02
`



You can use the following expression for birthdays

%%(diary-anniversary 11  2 1955) Daddy is %d years old

Ian.





[O] unset :no-expand for a subtree?

2014-03-28 Thread Rainer M Krug
Hi

I am using

,
| :Properties:
| :no-expand: TRUE
| :END:
`

for all my subtrees, except of one. So instead of specifying this for
all subtrees, I would like to use

,
| #+PROPERTY: no-expand TRUE
`

and in the one subtree, where I wand expansion, use something like

,
| :Properties:
| :no-expand: FALSE
| :END:
`

This obviously does not work, as :no-expand is still set. Is there a way
of un-setting it for a subtree?

Thanks,

Rainer

-- 
Rainer M. Krug
email: Raineratkrugsdotde
PGP: 0x0F52F982


pgpcpjSiUWzUe.pgp
Description: PGP signature


[O] Is there a way to change the home link and up link text when export to HTML?

2014-03-28 Thread KDr2
I want to change UP | HOME  to Archives | Categories for my blog, but I
do not know how to, for now I use javascript to change them after the page
loading in browser...

Thanks

-- 
-- 

KDr2, http://kdr2.com


[O] emphasis borders, double quotes, and export

2014-03-28 Thread Alan Schmitt
Hello,

I have removed the single and double quote characters from my
configuration of the emphasis borders:

#+begin_src emacs-lisp
  (setcar (nthcdr 2 org-emphasis-regexp-components)  \t\n,)
  (custom-set-variables `(org-emphasis-alist ',org-emphasis-alist))
#+end_src

However, the latex export of the following file is not correct.

--8---cut here---start-8---
This is a string: ~Nil~.
--8---cut here---end---8---

The generated latex is as follows (I show just the fragment of
interest):

#+begin_src latex
This is a string: \textasciitilde{}Nil\textasciitilde{}.
#+end_src

I see the same problem with html export.

Note that syntax highlighting works correctly.

Is this a bug?

Thanks,

Alan




Re: [O] org-agenda-do-date-late and emacs freeze

2014-03-28 Thread Igor Sosa Mayor
Am Thu, Mar 20, 2014 at 05:08:24PM +0100, Bastien schrieb:
 Hi Matt and all,
 
 thanks a lot for the detailed investigation -- I revisited the
 related problems and applied a fix.  Please let me know if you
 encoutner some glitches.

thanks  a lot. It seems to work perfectly!

-- 
:: Igor Sosa Mayor :: joseleopoldo1...@gmail.com ::
:: GnuPG: 0x1C1E2890   :: http://www.gnupg.org/  ::
:: jabberid: rogorido  ::::



Re: [O] Export Org checkboxes in ox-html using UTF-8 symbols

2014-03-28 Thread Sebastien Vauban
Rick Frankel wrote:
 BTW, i used [nbsp;] for the unchecked box (we use the same for
 checked and trans)... I think i'll change the unchecked box to
 #x2610; to match the checked box (same as sachua).

Isn't it error-prone and very misleading to have 3 different states in
the Org files, and just 2 different in the HTML exports?

Best regards,
  Seb

-- 
Sebastien Vauban




Re: [O] unset :no-expand for a subtree?

2014-03-28 Thread Rainer M Krug
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org
writes:

 Rainer M Krug wrote:
 ,
 | :Properties:
 | :no-expand: FALSE
 | :END:
 `

 This obviously does not work, as :no-expand is still set. Is there a way
 of un-setting it for a subtree?

 An idea: setting it to nil?  Untested...

I *guess* it will set the property to the string nil, but I'll try it
out.

Thanks,

Rainer


 Best regards,
   Seb

-- 
Rainer M. Krug
email: Raineratkrugsdotde
PGP: 0x0F52F982


pgpQ93UBVp438.pgp
Description: PGP signature


Re: [O] [PATCH] Add catch-up all LaTeX errors

2014-03-28 Thread Sebastien Vauban
Nicolas Goaziou wrote:
 Sebastien Vauban sva-n...@mygooglest.com
 writes:

 Isn't `orgfile' equal to `org-babel-exp-reference-buffer' in
 `org-latex-compile'?

 No, `org-babel-exp-reference-buffer' is a temporary buffer attached to
 no file. It cannot help to find original file.

OK. From reading the docstring, I thought it would contain the name of
the original buffer.

Best regards,
  Seb

-- 
Sebastien Vauban




[O] :no-expand not working on variables?

2014-03-28 Thread Rainer M Krug

Hi

shouldn't the following not give an error from R as it should not be
expanding the variables?

--8---cut here---start-8---
#+PROPERTY: no-expand TRUE
#+PROPERTY: var YEAR=2014

* a noexpand code

#+begin_src R :results output :no-expand
cat(YEAR)
#+end_src

#+RESULTS:
: 2014
--8---cut here---end---8---

The manual states:

,
| 14.8.2.11 `:no-expand'
| ..
| 
| By default, code blocks are expanded with `org-babel-expand-src-block'
| during tangling.  This has the effect of assigning values to variables
| specified with `:var' (see *Note var::), and of replacing noweb
| references (see *Note Noweb reference syntax::) with their targets.  The
| `:no-expand' header argument can be used to turn off this behavior.
`

Org-mode version 8.2.5h (release_8.2.5h-869-gdcfe09 @
/Users/rainerkrug/.emacs.d/org-mode/lisp/)

Cheers,

Rainer


-- 
Rainer M. Krug
email: Raineratkrugsdotde
PGP: 0x0F52F982


pgpXYrB9RBDhw.pgp
Description: PGP signature


[O] [bug] Org-verbatim and org-code not converted into HTML tags

2014-03-28 Thread Sebastien Vauban
Hello,

--8---cut here---start-8---
When =:hlines yes=, strips horizontal lines from the input table.

When ~:hlines yes~, strips horizontal lines from the input table.
--8---cut here---end---8---

outputs the following HTML:

--8---cut here---start-8---
pWhen =:hlines yes=, strips horizontal lines from the input
table./p

pWhen ~:hlines yes~, strips horizontal lines from the input
table./p
--8---cut here---end---8---

with Org-mode version 8.2.5h (release_8.2.5h-867-g25c591).

Test with minimal Emacs.

Best regards,
  Seb

-- 
Sebastien Vauban




Re: [O] [Patch] Few small fixes to html header

2014-03-28 Thread Marcin Antczak

Rick Frankel writes:

 On 2014-03-27 15:57, Marcin Antczak wrote:
 I've attached patch below, but I'm affraid that there is something
 wrong
 with indentation.
 I'm not sure if there is problem with my settings or just entire
 ox-html.el is indented badly.

 Unfortunately, ox-html is indented with a combination of tabs and
 spaces, you can turn on whitespace-mode to see. I'm not sure why your
 saving the file has touched areas you didn't edit. Did you do a
 re-indent or have a whitespace-cleanup or convert-tabs-to-spaces hook
 turned on?

No. I didn't.

Why ox-html is indented in a way that doesn't follow guidelines
described on Emacs Lisp Coding Conventions?

Could we fix it?


 My patch fixes HTML meta data produced on export by ox-html.el

 1. Meta charset definition should be set before title as document
 title can contain
 some unicode symbols etc.

 I believe this is the gist of your patch (bug fix?) -- putting the
 content-type declaration before the title (it's hard to tell due to
 all the changes in your patch)? If so, i don't see the need. Following
 is a sample org file w/ a unicode character in the title. It renders
 correctly on both internet explorer 9 and chrome 31.0.1650.63, the
 only browsers i have available right now. I believe that the meta
 content is parsed before the rendering, so the position within the
 header is irrelevant.

 #+BEGIN_SRC org
 ,#+TITLE: ☑ \gamma
 ,#+OPTIONS: toc:nil

 ,* Test utf-8 title
 Put  ☑ \gamma (checkbox and gamma) unicode characters in the title.
 #+END_SRC

But it's still bug.

1. Most modern browsers fallback to UTF-8 currently.
2. Charset is often set by server content type.

So, this is why you can see your example rendered correctly.
But there could be a case where it will not render properly.

From logical point of view - charset should be first. And it's in most
html frameworks such as HTML5 Boilerplate, Twitter Bootstrap etc.


 2. Added viewport declaration as described here:

 https://github.com/h5bp/html5-boilerplate/blob/v4.3.0/doc/html.md

 here:

 https://developer.apple.com/library/safari/documentation/AppleApplications/Reference/SafariWebContent/UsingtheViewport/UsingtheViewport.html

 I don't believe it's appropriate to have as a default in ox-html as
 the current exporter makes no attempt at responsive design. If you
 would like your exported documents to include it, you can use the
 HTML_HEAD_EXTRA property on a per-file basis, or customize the
 variable `org-html-head-extra'.

Ok.

I'm working on some exporter that outputs HTML with Twitter Bootstrap.
I'll implement this 'viewport' there.


 3. Fixed unnecessary \n at the end of Description meta.
 4. Removed unnecessary spaces in meta tags.

 Are these bugs or simply stylistic cleanup?

3. This is a bug for me. Meta shouldn't render closing  in new line.
4. Stylistics.

Marcin



Re: [O] Zotero: import HTML -- org syntax?

2014-03-28 Thread Ken Mankoff
On Fri, Mar 28, 2014 at 10:43 AM, Matt Price mopto...@gmail.com wrote:

 Hi,

 so, in my ponderously slow efforts to figure out a decent citation
 workflow for Org, I am trying for some modest integration with Zotero,
 which is the tool my humanities colleagues are most likely to use.

 I keep all of the references for my courses in a Zotero database.
 When generating a syllabus, I select a set of references, then copy
 them over to my org file.  However, then I have to edit each reference
 to give the appropriate italicization; in one of my courses we use APA
 citation formats, which I don't really know very well, and sometimes I
 make mistakes.


Doesn't Zotero offer an option to export to a BibTeX file and keep that
BibTeX file in sync? If so, you can just cite from the BibTeX file in Org
using RefTeX.

  -k.


Re: [O] Export Org checkboxes in ox-html using UTF-8 symbols

2014-03-28 Thread Rick Frankel

On 2014-03-28 10:01, Sebastien Vauban wrote:

Rick Frankel wrote:
BTW, i used [nbsp;] for the unchecked box (we use the same for
checked and trans)... I think i'll change the unchecked box to
#x2610; to match the checked box (same as sachua).

Isn't it error-prone and very misleading to have 3 different states in
the Org files, and just 2 different in the HTML exports?


There *are* three different states in the exported file -- the
transient mode is for partially completed rollups:

#+BEGIN_SRC org
,* rollup
- [-] All done
- [X] one
- [ ] two
#+END_SRC

Generates (abbreviated and indented):

#+BEGIN_SRC html
ul class=org-ul
licode[-]/code All done
ul class=org-ul
licode[X]/code one
/li
licode[#xa0;]/code two
/li
/ul
/li
/ul
#+END_SRC

rick



Re: [O] Export Org checkboxes in ox-html using UTF-8 symbols

2014-03-28 Thread Sebastien Vauban
Rick Frankel wrote:
 Isn't it error-prone and very misleading to have 3 different states in
 the Org files, and just 2 different in the HTML exports?

 There *are* three different states in the exported file -- the
 transient mode is for partially completed rollups:

OK, excellent!  Sorry for my misunderstanding.

Best regards,
  Seb

-- 
Sebastien Vauban




Re: [O] TODOs and birthdays

2014-03-28 Thread Ian Barton

On 28/03/14 16:02, Sharon Kimble wrote:

Ian Barton li...@wilkesley.net writes:


On 28/03/14 08:19, Sharon Kimble wrote:



And for the birthday TODOs, how can I include the date of birth so that it shows
their age please? Like -
,
| *** TODO Winnie Poohs birthday - is 83
| SCHEDULED: 2014-12-02 Tue AGE: 1930-12-02
`



You can use the following expression for birthdays

%%(diary-anniversary 11  2 1955) Daddy is %d years old

Ian.


I have this for my mums birthday

,
| *** SCHEDULED Mums birthday, she is %d years old
| %%(diary-anniversary 02-12-1930) Daddy is %d years old
| DEADLINE: 2014-12-02 Tue 12:00 SCHEDULED: 2014-12-02 Tue
| :END:
`

but it isn't giving any output, and btw, that is 2nd December. So how should it
be used then please?

Sharon.



I am pretty sure the date needs to be in the same format as my example:

%%(diary-anniversary 2 12 1930) Mum is %d years old

Have a look at http://orgmode.org/manual/Weekly_002fdaily-agenda.html 
for more info. Also http://orgmode.org/tmp/worg/org-faq.html contains 
lots of useful hints on how to do more complicated things like repeating 
appointments.


Ian.




Re: [O] emphasis borders, double quotes, and export

2014-03-28 Thread Nicolas Goaziou
Hello,

Alan Schmitt alan.schm...@polytechnique.org writes:

 Looking a little deeper into this, it seems to be a regression. I had
 files with things like ~'a list~ that exported correctly a couple weeks
 ago that no longer export correctly.

This should be fixed. Thank you.


Regards,

-- 
Nicolas Goaziou



Re: [O] TODOs and birthdays

2014-03-28 Thread Sharon Kimble
Ian Barton li...@wilkesley.net writes:

 On 28/03/14 08:19, Sharon Kimble wrote:


 And for the birthday TODOs, how can I include the date of birth so that it 
 shows
 their age please? Like -
 ,
 | *** TODO Winnie Poohs birthday - is 83
 | SCHEDULED: 2014-12-02 Tue AGE: 1930-12-02
 `


 You can use the following expression for birthdays

 %%(diary-anniversary 11  2 1955) Daddy is %d years old

 Ian.

I have this for my mums birthday

,
| *** SCHEDULED Mums birthday, she is %d years old
| %%(diary-anniversary 02-12-1930) Daddy is %d years old
| DEADLINE: 2014-12-02 Tue 12:00 SCHEDULED: 2014-12-02 Tue
| :END:
`

but it isn't giving any output, and btw, that is 2nd December. So how should it
be used then 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.3.1


pgp6uuQATNDDn.pgp
Description: PGP signature


[O] org-agenda-custom-command for property AND TODO state (for a cooking guide :) )

2014-03-28 Thread Xebar Saram
Hi all i was wondering if anyone knew how to set
a org-agenda-custom-command for property AND TODO state? that is create a
custom view that is similar to this sparse tree command:

C-c /  M   type=main/COOK

where it would match on type=main and have a COOK todo keyword

best

Z

P.S in case anyone wonders wth im using it for :) im trying to auto
generate a list of things to cook (todo word COOK) by type of meal so id
generate a list for main dishes, breakfast etc :)


Re: [O] :no-expand not working on variables?

2014-03-28 Thread Rainer M Krug
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org
writes:

 Rainer M Krug wrote:
 shouldn't the following not give an error from R as it should not be
 expanding the variables?

 #+PROPERTY: no-expand TRUE

 I guess this should be:

   #+PROPERTY: no-expand yes

Nope - the same.

Rainer


 Best regards,
   Seb

-- 
Rainer M. Krug
email: Raineratkrugsdotde
PGP: 0x0F52F982


pgpM7QWgJ_7OW.pgp
Description: PGP signature


Re: [O] [bug] Org-verbatim and org-code not converted into HTML tags

2014-03-28 Thread Nicolas Goaziou


Hello,

Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org
writes:

 When =:hlines yes=, strips horizontal lines from the input table.

 When ~:hlines yes~, strips horizontal lines from the input table.

 outputs the following HTML:

 pWhen =:hlines yes=, strips horizontal lines from the input
 table./p

 pWhen ~:hlines yes~, strips horizontal lines from the input
 table./p

 with Org-mode version 8.2.5h (release_8.2.5h-867-g25c591).

 Test with minimal Emacs.

This should be fixed. Thank you.


Regards,

-- 
Nicolas Goaziou




Re: [O] emphasis borders, double quotes, and export

2014-03-28 Thread Alan Schmitt
Nicolas Goaziou n.goaz...@gmail.com writes:

 Hello,

 Alan Schmitt alan.schm...@polytechnique.org writes:

 Looking a little deeper into this, it seems to be a regression. I had
 files with things like ~'a list~ that exported correctly a couple weeks
 ago that no longer export correctly.

 This should be fixed. Thank you.

I confirm it is, thanks a lot.

Alan



Re: [O] emphasis borders, double quotes, and export

2014-03-28 Thread Alan Schmitt
Alan Schmitt alan.schm...@polytechnique.org writes:

 Hello,

 I have removed the single and double quote characters from my
 configuration of the emphasis borders:

 #+begin_src emacs-lisp
   (setcar (nthcdr 2 org-emphasis-regexp-components)  \t\n,)
   (custom-set-variables `(org-emphasis-alist ',org-emphasis-alist))
 #+end_src

 However, the latex export of the following file is not correct.

 This is a string: ~Nil~.

 The generated latex is as follows (I show just the fragment of
 interest):

 #+begin_src latex
 This is a string: \textasciitilde{}Nil\textasciitilde{}.
 #+end_src

 I see the same problem with html export.

 Note that syntax highlighting works correctly.

 Is this a bug?

Looking a little deeper into this, it seems to be a regression. I had
files with things like ~'a list~ that exported correctly a couple weeks
ago that no longer export correctly.

Alan



Re: [O] Export Org checkboxes in ox-html using UTF-8 symbols

2014-03-28 Thread Rick Frankel

On 2014-03-27 04:43, Nicolas Goaziou wrote:

Hello,

Grant Rettke g...@wisdomandwonder.com writes:

Sacha Chua made a nice hack to export checkboxes as unicode symbols to
HTML here:

http://sachachua.com/blog/2014/03/emacs-tweaks-export-org-checkboxes-using-utf-8-symbols/?shareadraft=baba27119_533313c944f64

(defun sacha/org-html-checkbox (checkbox)
Format CHECKBOX into HTML.
(case checkbox (on span class=\check\#x2611;/span) ;
checkbox (checked)
(off span class=\checkbox\#x2610;/span)
(trans code[-]/code)
(t )))
(defadvice org-html-checkbox (around sacha activate)
(setq ad-return-value (sacha/org-html-checkbox (ad-get-arg 0

Thanks Sacha.

There is also:

(setq org-html-checkbox-type 'unicode)


You need a recent Org, though (maybe development version, I didn't 
check).


I didn't apply it in maint, so it's only in master.

BTW, i used [nbsp;] for the unchecked box (we use the same for 
checked and trans)... I think i'll change the unchecked box to #x2610; 
to match the checked box (same as sachua).


rick



[O] How to get rid of clocktable summary time in the form 2d 02:00

2014-03-28 Thread Buddy Butterfly

Hi,

I would like to have the summary times in a clocktable be displayed
only in hours, like 48:00 instead of 2d. Or, is it possible to
define that 1d corresponds to 8:00 as a working day? So in the
above example I would rather like to see 5d (workingdays) corresponding
to 40:00. Clocktable counts 1d as 24h (which is right ;-) but not
in business.

Thanks a lot,
Matt





Re: [O] :no-expand not working on variables?

2014-03-28 Thread Sebastien Vauban
Rainer M Krug wrote:
 shouldn't the following not give an error from R as it should not be
 expanding the variables?

 #+PROPERTY: no-expand TRUE

I guess this should be:

  #+PROPERTY: no-expand yes

Best regards,
  Seb

-- 
Sebastien Vauban




Re: [O] [Patch] Few small fixes to html header

2014-03-28 Thread Rick Frankel

On 2014-03-27 15:57, Marcin Antczak wrote:
I've attached patch below, but I'm affraid that there is something 
wrong

with indentation.
I'm not sure if there is problem with my settings or just entire
ox-html.el is indented badly.


Unfortunately, ox-html is indented with a combination of tabs and
spaces, you can turn on whitespace-mode to see. I'm not sure why your
saving the file has touched areas you didn't edit. Did you do a
re-indent or have a whitespace-cleanup or convert-tabs-to-spaces hook
turned on?


My patch fixes HTML meta data produced on export by ox-html.el

1. Meta charset definition should be set before title as document
title can contain
some unicode symbols etc.


I believe this is the gist of your patch (bug fix?) -- putting the
content-type declaration before the title (it's hard to tell due to
all the changes in your patch)? If so, i don't see the need. Following
is a sample org file w/ a unicode character in the title. It renders
correctly on both internet explorer 9 and chrome 31.0.1650.63, the
only browsers i have available right now. I believe that the meta
content is parsed before the rendering, so the position within the
header is irrelevant.

#+BEGIN_SRC org
,#+TITLE: ☑ \gamma
,#+OPTIONS: toc:nil

,* Test utf-8 title
Put  ☑ \gamma (checkbox and gamma) unicode characters in the title.
#+END_SRC


2. Added viewport declaration as described here:

https://github.com/h5bp/html5-boilerplate/blob/v4.3.0/doc/html.md

here:

https://developer.apple.com/library/safari/documentation/AppleApplications/Reference/SafariWebContent/UsingtheViewport/UsingtheViewport.html


I don't believe it's appropriate to have as a default in ox-html as
the current exporter makes no attempt at responsive design. If you
would like your exported documents to include it, you can use the
HTML_HEAD_EXTRA property on a per-file basis, or customize the
variable `org-html-head-extra'.


3. Fixed unnecessary \n at the end of Description meta.
4. Removed unnecessary spaces in meta tags.


Are these bugs or simply stylistic cleanup?

rick



Re: [O] [Patch] Few small fixes to html header

2014-03-28 Thread Marcin Antczak

Rick Frankel writes:

 On 2014-03-28 11:16, Marcin Antczak wrote:
 Rick Frankel writes:

 On 2014-03-27 15:57, Marcin Antczak wrote:
 I've attached patch below, but I'm affraid that there is something
 wrong
 with indentation.
 I'm not sure if there is problem with my settings or just entire
 ox-html.el is indented badly.

 Unfortunately, ox-html is indented with a combination of tabs and
 spaces, you can turn on whitespace-mode to see. I'm not sure why your
 saving the file has touched areas you didn't edit. Did you do a
 re-indent or have a whitespace-cleanup or convert-tabs-to-spaces hook
 turned on?

 Why ox-html is indented in a way that doesn't follow guidelines
 described on Emacs Lisp Coding Conventions?

 good question. I think because it's actually a very old file.

 Could we fix it?

 Another good question. Bastien- Do you think it makes sense to do a
 whitespace cleanup only commit of ox-html to master?

+1 from me.

 That may be, but it's a stylistic issue, not a bug. My read of the
 html dtd does not specify the order of elements in the head. Can you
 show me an example where the order of the elements causes incorrect
 display of the title?

Cannot reproduce this right now.
I had a lot of various problems with Polish Latin-2 ISO-8859-2
characters, but to be honest these were in pre-UTF era.

 Does it cause output which is incorrectly displayed? Otherwise it's
 not really a bug, but i will look at changing it the next time i need
 to touch the file.

There is no output from META tag. So, no.

But, w3c html-markup syntax documentation says:

end tags consist of the following parts, in exactly the following order:

A  character.
A / character
The element’s tag name.
Optionally, one or more space characters.
A  character.


They don't mention any newline character.


 I'm worried about touching (4) w/o tests, as sometimes attributes are
 concatenated, and removing a leading whitespace could cause breakage.

It shouldn't.
Meta tag can only have two attributes. There is no reason to concatenate
anything else.

 While source whitespace and output formatting are annoying, our
 approach to modifications of this (quite old) file has been to not
 make changes which don't materially affect functionality or fix bugs
 (the rule of least damage :).

I agree. But code really should be valid and IMHO little improvements
and code cleanups are ok.


Marcin



Re: [O] [Patch] Few small fixes to html header

2014-03-28 Thread Rick Frankel

On 2014-03-28 11:16, Marcin Antczak wrote:

Rick Frankel writes:

On 2014-03-27 15:57, Marcin Antczak wrote:
I've attached patch below, but I'm affraid that there is something
wrong
with indentation.
I'm not sure if there is problem with my settings or just entire
ox-html.el is indented badly.

Unfortunately, ox-html is indented with a combination of tabs and
spaces, you can turn on whitespace-mode to see. I'm not sure why your
saving the file has touched areas you didn't edit. Did you do a
re-indent or have a whitespace-cleanup or convert-tabs-to-spaces hook
turned on?

Why ox-html is indented in a way that doesn't follow guidelines
described on Emacs Lisp Coding Conventions?


good question. I think because it's actually a very old file.


Could we fix it?


Another good question. Bastien- Do you think it makes sense to do a
whitespace cleanup only commit of ox-html to master?



My patch fixes HTML meta data produced on export by ox-html.el

1. Meta charset definition should be set before title as document
title can contain
some unicode symbols etc.

But it's still bug.

1. Most modern browsers fallback to UTF-8 currently.
2. Charset is often set by server content type.

So, this is why you can see your example rendered correctly.
But there could be a case where it will not render properly.


Not true. This file renders incorrectly when opened from the file
system in ie 9 and chrome:

#+BEGIN_SRC html
html
head
title☑/title
/head
body
p☑ checkbox/p
/body
/html
#+END_SRC

But this one renders correctly:
#+BEGIN_SRC html
html
head
title☑/title
meta http-equiv=Content-Type content=text/html;charset=utf-8 /
/head
body
p☑ checkbox/p
/body
/html
#+END_SRC


From logical point of view - charset should be first. And it's in most
html frameworks such as HTML5 Boilerplate, Twitter Bootstrap etc.


That may be, but it's a stylistic issue, not a bug. My read of the
html dtd does not specify the order of elements in the head. Can you
show me an example where the order of the elements causes incorrect
display of the title?



2. Added viewport declaration as described here:

https://github.com/h5bp/html5-boilerplate/blob/v4.3.0/doc/html.md

here:

https://developer.apple.com/library/safari/documentation/AppleApplications/Reference/SafariWebContent/UsingtheViewport/UsingtheViewport.html

I don't believe it's appropriate to have as a default in ox-html as
the current exporter makes no attempt at responsive design. If you
would like your exported documents to include it, you can use the
HTML_HEAD_EXTRA property on a per-file basis, or customize the
variable `org-html-head-extra'.

Ok.

3. Fixed unnecessary \n at the end of Description meta.
4. Removed unnecessary spaces in meta tags.

Are these bugs or simply stylistic cleanup?

3. This is a bug for me. Meta shouldn't render closing  in new
line.


Does it cause output which is incorrectly displayed? Otherwise it's
not really a bug, but i will look at changing it the next time i need
to touch the file.

I'm worried about touching (4) w/o tests, as sometimes attributes are
concatenated, and removing a leading whitespace could cause breakage.

While source whitespace and output formatting are annoying, our
approach to modifications of this (quite old) file has been to not
make changes which don't materially affect functionality or fix bugs
(the rule of least damage :).

rick



[O] Zotero: import HTML -- org syntax?

2014-03-28 Thread Matt Price
Hi,

so, in my ponderously slow efforts to figure out a decent citation
workflow for Org, I am trying for some modest integration with Zotero,
which is the tool my humanities colleagues are most likely to use.

I keep all of the references for my courses in a Zotero database.
When generating a syllabus, I select a set of references, then copy
them over to my org file.  However, then I have to edit each reference
to give the appropriate italicization; in one of my courses we use APA
citation formats, which I don't really know very well, and sometimes I
make mistakes.

I can set up Zotero so that citations are copied in HTML.  That
preserves the markup I want to keep, but in a format that doesn't work
so well in an org document!  I would like to figure out a way to add
the citations with a single command that converts the HTML to org
markup.

so,

(1) is there already an HTML import function that I just don't know about?

(2) is anyone actually using Zotero for citations in org?  or have
people mostly given up and gone over to Bibtex instead?

Thanks very much,

Matt



Re: [O] Zotero: import HTML -- org syntax?

2014-03-28 Thread Rick Frankel

On 2014-03-28 10:43, Matt Price wrote:

Hi,

(1) is there already an HTML import function that I just don't know 
about?


Have you looked at pandoc:

http://johnmacfarlane.net/pandoc/

rick



Re: [O] A problem with publishing

2014-03-28 Thread Rick Frankel

On 2014-03-28 00:44, Marcin Borkowski wrote:

Dnia 2014-03-26, o godz. 09:26:15
Rick Frankel r...@rickster.com napisał(a):

On 2014-03-23 17:01, Marcin Borkowski wrote:
BTW, org-publish has built-in support for pushing to a remote server.
You can use a tramp url as the publishing-directory, bypassing the
completion function.

I know, but I read in the manual that it may not be the fastest thing
in the world.  (In fact, I use a very simple Makefile, which in turn
uses rsync, so it /might/ indeed be faster, not copying unnecessary
stuff.  Not sure whether Emacs+Tramp would do it.)



Org publish uses a timestamp cache, so while the wire protocol may be
slower, it doesn't copy unnecessary files and doesn't need to
communicate with the remote host to decide which files to copy.

Bonus of course is that the org-publish approach is self-contained
and reproducible.

rick



Re: [O] unset :no-expand for a subtree?

2014-03-28 Thread Sebastien Vauban
Rainer M Krug wrote:
 ,
 | :Properties:
 | :no-expand: FALSE
 | :END:
 `

 This obviously does not work, as :no-expand is still set. Is there a way
 of un-setting it for a subtree?

An idea: setting it to nil?  Untested...

Best regards,
  Seb

-- 
Sebastien Vauban




[O] bug#16751: 24.3.50; Export during Org export to HTML

2014-03-28 Thread Nicolas Goaziou
Hello,

Bastien b...@gnu.org writes:

 If someone wants to work on this, help is welcome.

 Let's keep the bug open in the meantime.

Unless I'm mistaken, the following patch should fix the issue.


Regards,

-- 
Nicolas Goaziou
From 4d62387fe035d9aa3d1dc96d12d40c53dca2afe5 Mon Sep 17 00:00:00 2001
From: Nicolas Goaziou n.goaz...@gmail.com
Date: Fri, 28 Mar 2014 19:24:38 +0100
Subject: [PATCH] Make Org links compatible with URI syntax

* lisp/org.el (org-make-link-regexps): Allow optional double slashes
  after type.  Small refactoring.

* testing/lisp/test-org-element.el (test-org-element/link-parser):
  Update test.

This patch allows to write both [[file:/file.org]] and [[file:///file.org]].
See bug#16751.
---
 lisp/org.el  | 43 ++--
 testing/lisp/test-org-element.el |  6 ++
 2 files changed, 21 insertions(+), 28 deletions(-)

diff --git a/lisp/org.el b/lisp/org.el
index bb83eb7..53f142e 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -5658,34 +5658,29 @@ stacked delimiters is N.  Escaping delimiters is not possible.
   Update the link regular expressions.
 This should be called after the variable `org-link-types' has changed.
   (setq org-link-types-re
-	(concat
-	 \\`\\( (mapconcat 'regexp-quote org-link-types \\|) \\):)
+	(concat \\` (regexp-opt org-link-types t) :\\(?://\\))
 	org-link-re-with-space
-	(concat
-	 ?\\( (mapconcat 'regexp-quote org-link-types \\|) \\):
-	 \\([^ org-non-link-chars  ]
-	 [^ org-non-link-chars ]*
-	 [^ org-non-link-chars  ]\\)?)
+	(concat ? (regexp-opt org-link-types t) :\\(?://\\)
+		\\([^ org-non-link-chars  ]
+		[^ org-non-link-chars ]*
+		[^ org-non-link-chars  ]\\)?)
 	org-link-re-with-space2
-	(concat
-	 ?\\( (mapconcat 'regexp-quote org-link-types \\|) \\):
-	 \\([^ org-non-link-chars  ]
-	 [^\t\n\r]*
-	 [^ org-non-link-chars  ]\\)?)
+	(concat ? (regexp-opt org-link-types t) :\\(?://\\)?
+		\\([^ org-non-link-chars  ]
+		[^\t\n\r]*
+		[^ org-non-link-chars  ]\\)?)
 	org-link-re-with-space3
-	(concat
-	 ?\\( (mapconcat 'regexp-quote org-link-types \\|) \\):
-	 \\([^ org-non-link-chars  ]
-	 [^\t\n\r]*\\))
+	(concat ? (regexp-opt org-link-types t) :\\(?://\\)?
+		\\([^ org-non-link-chars  ]
+		[^\t\n\r]*\\))
 	org-angle-link-re
-	(concat
-	 \\( (mapconcat 'regexp-quote org-link-types \\|) \\):
-	 \\([^ org-non-link-chars  ]
-	 [^ org-non-link-chars ]*
-	 \\))
+	(concat  (regexp-opt org-link-types t) :\\(?://\\)?
+		\\([^ org-non-link-chars  ]
+		[^ org-non-link-chars ]*
+		\\))
 	org-plain-link-re
 	(concat
-	 ( (mapconcat 'regexp-quote org-link-types \\|) \\):
+	 \\ (regexp-opt org-link-types t) :\\(?://\\)?
 	 (org-re \\([^ \t\n()]+\\(?:([[:word:]0-9_]+)\\|\\([^[:punct:] \t\n]\\|/\\)\\)\\)))
 	;;	 \\([^]\t\n\r() ]+[^]\t\n\r,.;() ]\\))
 	org-bracket-link-regexp
@@ -5693,7 +5688,7 @@ This should be called after the variable `org-link-types' has changed.
 	org-bracket-link-analytic-regexp
 	(concat
 	 \\[\\[
-	 \\(\\( (mapconcat 'regexp-quote org-link-types \\|) \\):\\)?
+	 \\( (regexp-opt org-link-types t) :\\(?://\\)?\\)?
 	 \\([^]]+\\)
 	 \\]
 	 \\(\\[ \\([^]]+\\) \\]\\)?
@@ -5701,7 +5696,7 @@ This should be called after the variable `org-link-types' has changed.
 	org-bracket-link-analytic-regexp++
 	(concat
 	 \\[\\[
-	 \\(\\( (mapconcat 'regexp-quote (cons coderef org-link-types) \\|) \\):\\)?
+	 \\( (regexp-opt (cons coderef org-link-types) t) :\\(?://\\)?\\)?
 	 \\([^]]+\\)
 	 \\]
 	 \\(\\[ \\([^]]+\\) \\]\\)?
diff --git a/testing/lisp/test-org-element.el b/testing/lisp/test-org-element.el
index def1659..72eea22 100644
--- a/testing/lisp/test-org-element.el
+++ b/testing/lisp/test-org-element.el
@@ -1362,12 +1362,10 @@ e^{i\\pi}+1=0
   ;; ... with expansion.
   (should
(equal
-//orgmode.org/worg
+orgmode.org/worg
 (org-test-with-temp-text [[Org:worg]]
   (let ((org-link-abbrev-alist '((Org . http://orgmode.org/;
-	(org-element-property
-	 :path
-	 (org-element-map (org-element-parse-buffer) 'link 'identity nil t))
+	(org-element-property :path (org-element-context))
   ;; ... with translation.
   (should
(equal
-- 
1.9.1



[O] Chapter headings

2014-03-28 Thread Steven Arntson
Hello, I'm a beginning org-mode user.

I'm writing a book with many chapters, each chapter as a top-level
header (*). Is there a way to assign chapter numbers automatically, such
that I might get a result along the lines of:

* 1. This is a chapter containing thousands of words.

* 2. This is the next chapter, with many words.

* 3. And so on.

Thank you!
steven arntson




Re: [O] Chapter headings

2014-03-28 Thread Nick Dokos
Steven Arntson ste...@stevenarntson.com writes:

 Hello, I'm a beginning org-mode user.

 I'm writing a book with many chapters, each chapter as a top-level
 header (*). Is there a way to assign chapter numbers automatically, such
 that I might get a result along the lines of:

 * 1. This is a chapter containing thousands of words.

 * 2. This is the next chapter, with many words.

 * 3. And so on.


There are probably many ways to do that, but I want to invert the
question: *why* do you want chapter numbers in your org file?
I would argue that they are a bad idea in the vast majority of cases.

Nick






Re: [O] Chapter headings

2014-03-28 Thread Steven Arntson
Nick Dokos ndo...@gmail.com writes:

 There are probably many ways to do that, but I want to invert the
 question: *why* do you want chapter numbers in your org file?
 I would argue that they are a bad idea in the vast majority of cases.

 Nick

I'm just accustomed to seeing them in my working drafts. Perhaps it is I
who needs to change, rather than my unnumbered chapters! Something I
haven't explored yet with org-mode is exporting to LaTeX, but it sounds
like these numbers can be made to appear after export. I'm not yet a
LaTeX user, so I may wait to explore that until I get to it.

Best!
steven




Re: [O] Space in Exported Text

2014-03-28 Thread Sam Flint

#part sign=pgpmime
You know, at this point, I'm surprised no-one has mentioned org-mime.
It works great, and let's you use tables, and just about any feature.














foo
bar
quux




1
2
3



4
5
6






Sam Flint
swfl...@flintfam.org
freenode: swflint
sip:swfl...@ekiga.net
XMPP: swfl...@flintfam.org
http://flintfam.org/~swflint
2048D/BAFBF3FF
(3696 0D80 EC3C D40A 0186  D0E8 C63B 96FB BAFB F3FF)



[O] Proposal to replace the prefix repetition with whitespace during expansion of noweb references

2014-03-28 Thread Pontus Michael
I would like to propose a change to the behavior of noweb expansion in
relation to prefix handling. Current behavior intends to insert the text
preceding noweb reference before every successive line of referenced
code.

For instance the expansion of following source block:

#+begin_src emacs-lisp :noweb yes
(concat foo)
#+end_src

In presence of this source block:

#+begin_src emacs-lisp :noweb-ref foo
foo
bar
#+end_src

Will result in code from next source block:

#+begin_src emacs-lisp
(concat foo
(concat bar)
#+end_src

I recommend to introduce a change that will replace the inserted prefix
with whitespace of equal length. If it was the case then provided
example would produce the following code after expansion:

#+begin_src emacs-lisp
(concat foo
bar)
#+end_src

Here are the arguments in support of my proposal:

1) The proposed behavior is identical to one produced by original noweb.

2) Documentation provides a reasoning for current behavior as an example
   of reference expansion after the introduction of single-line comment
   with intention to comment all the lines caught in expansion. This
   reasoning follows simplistic assumption of semantics of arbitrary
   language and takes advantage of the single line comment notation used
   for non-intended purpose (i.e. multiline comment should have been
   used instead).

3) Continuing the line of examples given in emacs lisp, which lacks the
   notation for multiline comments I fail to see a situation where
   docstrings would not only serve the intended purpose, but in many
   cases contribute to quality and readability of the code.

4) Current behavior lacks the mechanism for handling multiple noweb
   references present on the same line. If prefix would be extracted
   from the unexpanded code and expansion would include raw noweb
   references notation. Clearly this is unexpected behavior.

If my proposal will find support in the community I can put my own
effort in bringing this change into existence.


[O] Images in tables?

2014-03-28 Thread Peter Davis


I'm finishing a PDF document that will contain a number of screen shots. 
I'd like to put them in a table to avoid just having them arranged 
vertically on the page. Is there a way to do that?


Specifically, I'm using

#+ATTR_LATEX: :height 6cm

to set the heights of the images. Can that work with a table somehow?

Thanks!

-pd


--

Peter Davis
The Tech Curmudgeon
www.techcurmudgeon.com




Re: [O] Chapter headings

2014-03-28 Thread Alan Tyree
Unless you have the structure of your book set in stone, numbers just get
in your way. The great power of org is being able to write 'modularly' and
rearrange at will.

When you export, your chapter/section numbers will be right as well as all
cross references.

I think you'll be happier to ignore numbered headings when writing. I've
just moved to org for a 600+ page book -- Magic (and even more magic once
the whole bibliographic reference problem is solved).

Cheers,
Alan


On 29 March 2014 07:49, Steven Arntson ste...@stevenarntson.com wrote:

 Nick Dokos ndo...@gmail.com writes:

  There are probably many ways to do that, but I want to invert the
  question: *why* do you want chapter numbers in your org file?
  I would argue that they are a bad idea in the vast majority of cases.
 
  Nick

 I'm just accustomed to seeing them in my working drafts. Perhaps it is I
 who needs to change, rather than my unnumbered chapters! Something I
 haven't explored yet with org-mode is exporting to LaTeX, but it sounds
 like these numbers can be made to appear after export. I'm not yet a
 LaTeX user, so I may wait to explore that until I get to it.

 Best!
 steven






-- 
Alan L Tyreehttp://www2.austlii.edu.au/~alan
Tel:  04 2748 6206


Re: [O] Chapter headings

2014-03-28 Thread Steven Arntson
Back in my mac-user days I used a program called Scrivener that would
renumber chapters on the fly if I dragged them to new positions. I think
I was missing that functionality a little, but now that I think about
it, I shouldn't miss it. It didn't add anything. My next project will be
to learn more about exporting. I'm sure I will have questions as I
encounter that ...





Re: [O] TODOs and birthdays

2014-03-28 Thread Eric Abrahamsen
Sharon Kimble boudic...@talktalk.net writes:

 I have a document called 'organiser.org' which is mainly comprised of various
 TODOs under various projects, and various NEXT under birthdays and hospital
 appointments. These TODOs can be up to 4 levels in depth, and with one level 1
 TODO as the project header. How can all of these TODOs be included in the 
 agenda
 please?

 And for the birthday TODOs, how can I include the date of birth so that it 
 shows
 their age please? Like - 
 ,
 | *** TODO Winnie Poohs birthday - is 83
 | SCHEDULED: 2014-12-02 Tue AGE: 1930-12-02
 `

 Thanks
 Sharon.

Do you use bbdb by any chance? If you do, you can put the birthday on
the person's record, as an anniversary field that looks like, for
example:

anniversary: 1930-12-02 birthday

It will show up properly in org agendas with the following settings
(hope I haven't forgotten anything):

(require 'bbdb-anniv)
(setq org-agenda-include-diary t)
(add-hook 'diary-list-entries-hook 'bbdb-anniv-diary-entries)

Just another option...

Eric




Re: [O] Images in tables?

2014-03-28 Thread Feng Shu
Peter Davis p...@pfdstudio.com writes:

 I'm finishing a PDF document that will contain a number of screen
 shots. I'd like to put them in a table to avoid just having them
 arranged vertically on the page. Is there a way to do that?

#+MACRO:  p   \includegraphics[scale=1]{$1}

| {{{p(a.png)}}} | {{{p(b.png)}}} |
| {{{p(c.png)}}} | {{{p(d.png)}}} |



 Specifically, I'm using

 #+ATTR_LATEX: :height 6cm

 to set the heights of the images. Can that work with a table somehow?

 Thanks!

 -pd

-- 




Re: [O] mobile-org http links not recognized on iPhone

2014-03-28 Thread Chris Henderson
If my link is like: [[http://orgmode.org]] - MobileOrg's view as document
mode doesn't recognize this as a valid link. It only does that if the link
is in [[link][description]] format. Is there any way around this?

Thanks.


On Tue, Mar 18, 2014 at 3:26 AM, Sean Escriva sean.escr...@gmail.comwrote:


 Chris Henderson henders...@gmail.com writes:

  http links on mobile-org on iPhone is not click-able and I need to select
  all, copy and paste the link on safari instead of just clicking and
 opening
  it directly. Is this normal behavior?

 No links should be clickable, they are for me. For example, with the
 following link in my one of my org agenda files:

   - [[http://queue.acm.org/detail.cfm?id%3D2413037][Thinking Methodically
 about Performance]]

 In MobilOrg I can view the node in the doc, using the right arrow, and
 then choose View as Document. The links are clickable in this view, as
 other views assume editing.

 --
 -sean



[O] Reference to org-drawers in the manual

2014-03-28 Thread Nick Dokos
Section 15.6, Summary of in-buffer settings, contains a reference to
org-drawers which if I'm not mistaken no longer exists:

`#+DRAWERS: NAME1 ...'
 Set the file-local set of additional drawers.  The corresponding
 global variable is `org-drawers'.

-- 
Nick