[O] Accents Issues in Table formula in French.
Hello, I have an issue with remote function in formula : #+TBLNAME: ch-mdp-août-2013 |---+--++---+---+--+---+--++--+| | | 2013 | août | Lundi | Mardi | Mercredi | Jeudi | Vendredi | Samedi | Dimanche || |---+--++---+---+--+---+--++--+| | | sem | jour |19 |20 | 21 |22 | 23 | 24 | 25 | Stotal | | # | s33 | charge | | |1 | 1 |1 | | | 3 | |---+--++---+---+--+---+--++--+| | | sem | jour |26 |27 | 28 |29 | 30 | 31 | || | # | s34 | charge | | 1 | | | | | | 1 | |---+--++---+---+--+---+--++--+| | # | Mois || | | | | | | | 4 | |---+--++---+---+--+---+--++--+| #+TBLFM: $11=vsum($4..$>>)::@>$11=vsum(@<..@>>);N * ch-mdp-total-2013 #+TBLNAME: ch-mdp-total |---+| | mois | charge | |---+| | août | 3 | |---+| | total | 3 | |---+| #+TBLFM: @2$2=remote(ch-mdp-août-2013, @>$>)::@>$2=vsum(@<<..@>>) give me : when I update : #+TBLNAME: ch-mdp-total |---+| | mois | charge | |---+| | août | #ERROR | |---+| | total | #ERROR | |---+| #+TBLFM: @2$2=remote(ch-mdp-août-2013, @>$>)::@>$2=vsum(@<<..@>>) debug formula : Substitution history of formula Orig: remote(ch-mdp-août-2013, @>$>) $xyz-> remote(ch-mdp-août-2013, @>$>) @r$c-> remote(ch-mdp-août-2013, @>$>) $1->remote(ch-mdp-août-2013, @>$>) ^ Error: Expected `)' Orig: vsum(@2..@2) $xyz-> vsum(@2..@2) @r$c-> vsum((#ERROR)) $1->vsum((#ERROR)) --^ Error: #'s not allowed in this context Thanks for help -- flav
Re: [O] koma letter exporter: changing the priority of options
Hello Rasmus,
Sorry for the delay, I was in vacations with tethering-only internet
access.
ras...@gmx.us writes:
> The following message is a courtesy copy of an article
> that has been posted to gmane.emacs.orgmode as well.
>
> Rasmus writes:
>
>> Alan,
>>
>>> alan.schm...@polytechnique.org writes:
>>>
Yes, this is not satisfactory (and the email and author is also
problematic in this regard). We need to know whether an option was set
in the file, independently of its default value. Is there a way to do
this?
>>>
>>> Thanks to Nicolas, I've been able to create a cleaner solution: we track
>>> some of the variables (ones for which we currently output something by
>>> default, typically because they are set or because we choose to always
>>> output something, like from-phone), and we only output the code if the
>>> variable was set in the file. Thus if nothing is set, the lco file
>>> wins. Note that with this approach, one can have a default in the lco
>>> that is overridden by the file, for instance for foldmarks or to display
>>> phone numbers.
>>>
>>> Regarding the name and email, we output it before the lco if they are
>>> not specified in the file, and after if they are.
>>>
>>> What do you think of this approach? Are there other variables we should
>>> track?
>
> I spoke too early. For example this letter no longer works as usual:
>
> #+TITLE: test
> #+OPTIONS: foldmarks:nil
> * Letter
> my letter
> ** TO :TO:
>someone
>somewhere
>
> But this is because nil has a "new" meaning of "not set" as opposed to
> "false". Is this OK? On one hand nil usually means False in ox, I
> think (e.g. inline:nil → inline comments not posted), but on the other
> hand nil often means not set in Emacs. . . It is nice to having to
> look at the extra setkomavariable, but I'm not sure whether it's
> right.
I tried to fix it in the updated attached patch. I set a default value
of "foldmarks-not-set" to the predicate that detects if it is set in the
file, then I compare its contents. This assumes that the user will not
give this literal value to the option.
> I also find something like this ghastly:
>
> (unless author-set
> (when author (format "\\setkomavar{fromname}{%s}\n"
>(org-export-data author info
> (unless email-set
> (when email (format "\\setkomavar{fromemail}{%s}\n" email)))
> ^^
> ;; Letter Class Option File
> (when lco
> [...]
> ))
> ;; Define "From" data.
> (when (and author author-set) (format "\\setkomavar{fromname}{%s}\n"
> (org-export-data author info)))
> (when from-address (format "\\setkomavar{fromaddress}{%s}\n"
> from-address))
> (when phone-number
> (format "\\setkomavar{fromphone}{%s}\n" phone-number))
> (when (and email email-set) (format "\\setkomavar{fromemail}{%s}\n"
> email))
> ^
>
> But perhaps it is the only way to get what you want.
I could not find a way to do it another way, but I'll gladly take any
suggestion. What we want is:
- if email is set in the file, use it;
- otherwise, use the one from the lco;
- otherwise, use the default one.
> Also, with the current setup, I can only set email before or after.
> Why? What if I want to let PLACE be dependent on my LCO file versus
> my org file?
I think you can do it: if you don't give the option in the file, the one
from the LCO will be used, otherwise the one in the file will override
it. The main thing with author and email is that they almost always have
non-nil default values, whereas place's default value is nil. If this is
not correct, we can extend the approach for author and email to places
or other options.
Best,
Alan
>From 1299e543992d00f98d52a967c5a802213ce09799 Mon Sep 17 00:00:00 2001
From: Alan Schmitt
Date: Mon, 22 Jul 2013 16:46:02 +0200
Subject: [PATCH] Koma exporter: Ensure customization to LCO files are taken
into account
* contrib/lisp/ox-koma-letter.el: Change default values to match the scrlttr2
default values. Track which options are set in the file and only output the
corresponding options when they are changed.
---
contrib/lisp/ox-koma-letter.el | 49 +++---
1 file changed, 37 insertions(+), 12 deletions(-)
diff --git a/contrib/lisp/ox-koma-letter.el b/contrib/lisp/ox-koma-letter.el
index d149f9d..9ae4d32 100644
--- a/contrib/lisp/ox-koma-letter.el
+++ b/contrib/lisp/ox-koma-letter.el
@@ -228,7 +228,7 @@ English manual of 2012-07-22)"
-(defcustom org-koma-letter-use-backaddress t
+(defcustom org-koma-letter-use-backaddress nil
"Print return address in small line above to address."
:group 'org-export-koma-letter
:type 'boolean)
@@ -243,12 +243,12 @@ Use `foldmarks:true' to activate default fold marks or
:group 'org-export-koma-letter
:type 'string)
-(defcustom org-koma-letter-use-phone t
+(d
Re: [O] koma letter exporter: changing the priority of options
alan.schm...@polytechnique.org writes:
> I tried to fix it in the updated attached patch. I set a default value
> of "foldmarks-not-set" to the predicate that detects if it is set in the
> file, then I compare its contents. This assumes that the user will not
> give this literal value to the option.
The attached version is updated to apply cleanly on master (after
applying your other patches).
Alan
>From 6c930ee3cca8db5af333e8822686f7783e72c14b Mon Sep 17 00:00:00 2001
From: Alan Schmitt
Date: Mon, 22 Jul 2013 16:46:02 +0200
Subject: [PATCH] Koma exporter: Ensure customization to LCO files are taken
into account
* contrib/lisp/ox-koma-letter.el: Change default values to match the scrlttr2
default values. Track which options are set in the file and only output the
corresponding options when they are changed.
---
contrib/lisp/ox-koma-letter.el | 49 +++---
1 file changed, 37 insertions(+), 12 deletions(-)
diff --git a/contrib/lisp/ox-koma-letter.el b/contrib/lisp/ox-koma-letter.el
index 6f5529f..240de29 100644
--- a/contrib/lisp/ox-koma-letter.el
+++ b/contrib/lisp/ox-koma-letter.el
@@ -232,7 +232,7 @@ English manual of 2012-07-22)."
-(defcustom org-koma-letter-use-backaddress t
+(defcustom org-koma-letter-use-backaddress nil
"Print return address in small line above to address."
:group 'org-export-koma-letter
:type 'boolean)
@@ -247,12 +247,12 @@ Use `foldmarks:true' to activate default fold marks or
:group 'org-export-koma-letter
:type 'string)
-(defcustom org-koma-letter-use-phone t
+(defcustom org-koma-letter-use-phone nil
"Print sender's phone number."
:group 'org-export-koma-letter
:type 'boolean)
-(defcustom org-koma-letter-use-email t
+(defcustom org-koma-letter-use-email nil
"Print sender's email address."
:group 'org-export-koma-letter
:type 'boolean)
@@ -299,9 +299,11 @@ A headline is only used if #+OPENING is not set. See also
org-koma-letter-default-class
org-latex-default-class) t)
(:author "AUTHOR" nil (org-koma-letter--get-value org-koma-letter-author) t)
+(:author-changed-in-buffer-p "AUTHOR" nil nil t)
(:from-address "FROM_ADDRESS" nil nil newline)
(:phone-number "PHONE_NUMBER" nil org-koma-letter-phone-number)
(:email "EMAIL" nil (org-koma-letter--get-value org-koma-letter-email) t)
+(:email-changed-in-buffer-p "EMAIL" nil nil t)
(:to-address "TO_ADDRESS" nil nil newline)
(:place "PLACE" nil org-koma-letter-place)
(:opening "OPENING" nil org-koma-letter-opening)
@@ -318,9 +320,13 @@ A headline is only used if #+OPENING is not set. See also
(:with-after-letter nil "after-letter-order"
org-koma-letter-special-tags-after-letter)
(:with-backaddress nil "backaddress" org-koma-letter-use-backaddress)
+(:with-backaddress-changed-in-buffer-p nil "backaddress" nil)
(:with-foldmarks nil "foldmarks" org-koma-letter-use-foldmarks)
+(:with-foldmarks-changed-in-buffer-p nil "foldmarks" "foldmarks-not-set")
(:with-phone nil "phone" org-koma-letter-use-phone)
+(:with-phone-changed-in-buffer-p nil "phone" nil)
(:with-email nil "email" org-koma-letter-use-email)
+(:with-email-changed-in-buffer-p nil "email" nil)
(:with-place nil "place" org-koma-letter-use-place)
(:with-subject nil "subject" org-koma-letter-subject-format))
:translate-alist '((export-block . org-koma-letter-export-block)
@@ -540,11 +546,19 @@ holding export options."
info)))
(let ((lco (plist-get info :lco))
(author (plist-get info :author))
+ (author-set (plist-get info :author-changed-in-buffer-p))
(from-address (org-koma-letter--determine-to-and-from info 'from))
(phone-number (plist-get info :phone-number))
(email (plist-get info :email))
+ (email-set (plist-get info :email-changed-in-buffer-p))
(signature (plist-get info :signature)))
(concat
+ ;; author or email not set in file: may be overridden by lco
+ (unless author-set
+ (when author (format "\\setkomavar{fromname}{%s}\n"
+ (org-export-data author info
+ (unless email-set
+ (when email (format "\\setkomavar{fromemail}{%s}\n" email)))
;; Letter Class Option File
(when lco
(let ((lco-files (split-string lco " "))
@@ -553,11 +567,12 @@ holding export options."
(setq lco-def (format "%s\\LoadLetterOption{%s}\n" lco-def lco-file)))
lco-def))
;; Define "From" data.
- (when author (format "\\setkomavar{fromname}{%s}\n"
- (org-export-data author info)))
+ (when (and author author-set) (format "\\setkomavar{fromname}{%s}\n"
+ (org-export-data author info)))
(when from-address (format "\\setkomavar{fromaddress}{%s}\n" from-address))
- (when phone-number (format "\\setkomavar{fromphone}{%s}\n" phone-number))
- (when email (format "\\setkomavar{fromemail}{%s}\n" email))
+ (when phone-number
+ (format "\\setkomavar{fromphone}{%s}\n" phone-number))
+ (when (
[O] how to check/uncheck all checkboxes
The typical structure as following: - [-] root - [ ] b - [X] c - [ ] d What i want is: if I toggle the root, all checkboxes, including root and children, toggled, no matter the children's status are. Is there native function/command do things like this? -- Jun Fang 方俊
Re: [O] [PATH] [NEW EXPORTER] two slide backends for contrib
On 2013-08-27 00:41, Matt Price wrote: I just came across this, having missed it in February. Rick, I was wondering if you had thought about enabling some of deck.js's snazzier features -- transitions for text elements, for instance, like we see in the intro deck here: http://imakewebthings.com/deck.js/#intro I'm mostly asking because I'd like to try and copy your work to make an exporter for impress.js (https://github.com/bartaz/impress.js). Kinjo has written one, but it uses the old exporter and no longer works with current versions of org, so I thought I would start with your deck.js work. I know that's not very specific, but if you've thought about these issues I would love to learn wat you've figured out. Thanks! All the fancy transitions and builds in the deck.js intro are handled via CSS. So, the exporter will handle them easily. If you look at the source for the intro, you will see that all the builds and transitions are defined in home.css, and applied based on slide id and/or class. If you look at the documentation for ox-deck @https://github.com/cybercode/org-slides, you will see that you can specify per-slide classes via the HTML_CONTAINER_CLASS property on the headline (and any headline can be build by setting the "slide" class on the headline). Taking a quick look @ the impress.js docs, i noticed that there is an S9 template for impress.js (http://slideshow-s9.github.io/slideshow-impress.js), and that everything is specified w/ slide properties (x, y, z, scale and rotate), so I would use headline PROPERTIES ( :IMPRESS_X, etc) to define the slideshow. Also note that it might be easier to inherit from ox-s5 instead of ox-deck as it is more generic (and add a wrapper around `org-s5-headline') to process the additional properties. rick
[O] [BUG] hline handling in ob-ruby
Eric- There is a bug in ob-ruby --- if an literal 'hline is passed into (e.g., :hline no) a ruby block, the execution fails due to an incorrect datatype (this is not an issue in any other language). The patch provided in http://lists.gnu.org/archive/html/emacs-orgmode/2013-08/msg00316.html (and reattached here), applies the solution used in ox-python to handle the issue. An alternative solution is ok too :). I would be glad to apply the patch myself, but since you are the owner of the file i would appreciate you ok before proceeding. tia, rickFrom 4ae86a04680bcf671d43bb0b70bfddd083b743b2 Mon Sep 17 00:00:00 2001 From: Rick Frankel Date: Thu, 15 Aug 2013 14:43:51 -0400 Subject: [PATCH] Handle literal 'hline arguments passed to ruby. Solution shamelessly copied from ob-python. * lisp/ob-ruby.el: New customizations `org-babel-ruby-hline-to' and `org-babel-ruby-nil-to' (org-babel-ruby-var-to-ruby): Convert incoming 'hlines. (org-babel-ruby-table-or-string): Convert outgoing nils. --- lisp/ob-ruby.el | 26 -- 1 file changed, 24 insertions(+), 2 deletions(-) diff --git a/lisp/ob-ruby.el b/lisp/ob-ruby.el index 20fb418..d15d288 100644 --- a/lisp/ob-ruby.el +++ b/lisp/ob-ruby.el @@ -50,6 +50,20 @@ (defvar org-babel-ruby-command "ruby" "Name of command to use for executing ruby code.") +(defcustom org-babel-ruby-hline-to "nil" + "Replace hlines in incoming tables with this when translating to ruby." + :group 'org-babel + :version "24.4" + :package-version '(Org . "8.0") + :type 'string) + +(defcustom org-babel-ruby-nil-to 'hline + "Replace 'nil' in ruby tables with this before returning." + :group 'org-babel + :version "24.4" + :package-version '(Org . "8.0") + :type 'string) + (defun org-babel-execute:ruby (body params) "Execute a block of Ruby code with Babel. This function is called by `org-babel-execute-src-block'." @@ -115,13 +129,21 @@ Convert an elisp value into a string of ruby source code specifying a variable of the same value." (if (listp var) (concat "[" (mapconcat #'org-babel-ruby-var-to-ruby var ", ") "]") -(format "%S" var))) +(if (equal var 'hline) + org-babel-ruby-hline-to + (format "%S" var (defun org-babel-ruby-table-or-string (results) "Convert RESULTS into an appropriate elisp value. If RESULTS look like a table, then convert them into an Emacs-lisp table, otherwise return the results as a string." - (org-babel-script-escape results)) + ((lambda (res) + (if (listp res) + (mapcar (lambda (el) (if (equal el 'nil) + org-babel-ruby-nil-to el)) + res) + res)) + (org-babel-script-escape results))) (defun org-babel-ruby-initiate-session (&optional session params) "Initiate a ruby session. -- 1.8.0
Re: [O] Carriage return in macro
At Mon, 26 Aug 2013 12:16:53 +0200, Nicolas Goaziou wrote: > > Is there any way to have carriage returns within the text of the > > macro ? > > No, there isn't. Macros target small substitutions. > > > I have already tried using the #+BEGIN_ODT...#+END_ODT construct, but that > > *really* messes with the format of the text within it. > > What do you mean? I don't know odt exporter very well, but contents of > the block should be included as-is. > If I put several lines into an #+BEGIN_ODT..#+END_ODT block, all whitespace formating is lost. A list like - List one - List two - List three becomes - List one - List two - List three This is why I started puting the formatting on each line, and rather than type all of the
[O] lexical-binding is not set for org src mode
elisp code blocks do not recognize lexical-binding in org src edit mode. For example, if I press C-c . on the following block, the buffer does not have lexical-binding set to t. #+BEGIN_SRC elisp ;; -*- lexical-binding: t; -*- (message "%S" lexical-binding) #+END_SRC Is there a workaround?
Re: [O] Carriage return in macro
Hello, Tim writes: > If I put several lines into an #+BEGIN_ODT..#+END_ODT block, all whitespace > formating is lost. A list like > > - List one > - List two > - List three > > becomes > > - List one - List two - List three I don't quite understand. You are expected to put valid odt code within an ODT block. You may be after an example block? Regards, -- Nicolas Goaziou
[O] Escaping an underscore in LaTeX export
LaTeX recommends \_ as an "escaped" underscore. In other words,
"really use the underscore, not a subscript." When I do this in
Org-mode and export via =C-e l p=, I don't get that behavior.
Here's my options header:
#+OPTIONS: *:t TeX:t LaTeX:t
a\_b -> a$\backslash$$_{\text{b}}$
a$\_$b -> a\$\_\$b
a $\_$ b -> a $\_$ b
What *does* work, is this:
a\(\_\)b -> a\_b
If this is the best/only way, that's okay. However, if others believe
that it should be passed through as \_ to LaTeX, perhaps that's the
best way? After all, just passing along _ works to subscript whenever
and wherever with my tex:t and latex:t options... perhaps escaping it
should also work?
An analog might be the use of \$, which escapes the dollar sign and
passes it through to appear as a dollar sign in the final document. I
suppose I'd make the case that if that's interpreted to be escaping
(vs. converting it to $\backslash$$), then perhaps escaping an
underscore should be treated the same.
Fringe use that I just stumbled on and isn't a critical issue, but I
thought I'd mention it.
Re: [O] Escaping an underscore in LaTeX export
Hello,
John Hendy writes:
> LaTeX recommends \_ as an "escaped" underscore. In other words,
> "really use the underscore, not a subscript." When I do this in
> Org-mode and export via =C-e l p=, I don't get that behavior.
>
> Here's my options header:
>
> #+OPTIONS: *:t TeX:t LaTeX:t
>
> a\_b -> a$\backslash$$_{\text{b}}$
> a$\_$b -> a\$\_\$b
> a $\_$ b -> a $\_$ b
>
> What *does* work, is this:
>
> a\(\_\)b -> a\_b
You can use the entity : \under{}, e.g.
a\under{}b
or limit subscript to _{...} constructs., e.g.,
#+options: ^:{}
a_b
Regards,
--
Nicolas Goaziou
Re: [O] lexical-binding is not set for org src mode
On Wed, Aug 28, 2013 at 03:53:39AM +0900, Jisang Yoo wrote: > elisp code blocks do not recognize lexical-binding in org src edit > mode. For example, if I press C-c . on the following block, the buffer > does not have lexical-binding set to t. > > #+BEGIN_SRC elisp > ;; -*- lexical-binding: t; -*- > > (message "%S" lexical-binding) > #+END_SRC > I think this is because org-edit-special lets you edit in an indirect buffer. I do not thing property lines are respected in indirect buffers. -- Suvayu Open source is the future. It sets us free.
[O] [bug] [babel] babel corrupts undo history
c-c ' c-c ' on this. then undo or undo-tree-undo.
what happens is data corruption. to me, undo is a low-level
operation that should always work, even with a syntactically
invalid block.
a relevant variable is org-src-preserve-indentation. it is
possible to change it without changing a block.
===
#+BEGIN_SRC sh :noweb yes :results verbatim output
(
cat <&1
:
#+END_SRC
===
Emacs 24.2, recent Org, recent undo-tree-mode.
Thanks.
Samuel
P.S. You might be wondering why I use a subshell and a
redirection followed by a null command. This is because I
prefer to bypass Babel's error mechanism, which I find
confusing. Doing exactly as above is the only way I know to
get Babel to work the way I prefer (although {} might or
might not work also). I always do this for every block. IMO it would
be great for newcomers if there were options in Babel sh blocks for
exactly this.
--
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] [bug] org-refile makes ido think that some candidates are directories
org-refile makes ido think that every entry that is in the current buffer is a directory, while every entry that is in another buffer is a file. === You can confirm by loading ido and doing this: (setq org-refile-use-outline-path t) (setq org-outline-path-complete-in-steps nil) (setq org-completion-use-ido t) Now do org-refile and look at the candidate list. Please note the addition of the filename at the end of the entries that are not in the current buffer, and probably a different font. You can use the ido keys for navigating directories, and they will only go to the entries in the current buffer. === The relevant part of org.el seems to be this, but I do not understand it: (setq answ (funcall cfunc prompt tbl nil (not new-nodes) nil 'org-refile-history (or cdef (car org-refile-history This is FAR beyond my ability to debug, but I suspect that the artificial distinction between the current buffer and other buffers, treating one as a directory and the other as a file, might be related to several long-standing, subtle but extremely annoying bugs involving the default and history. But I could be wrong about that. For example, if you previously refiled, there is always an extra entry that has no marker and errors if you select it, and it is often the default candidate :(. And it is impossible to narrow to a subtree of the default subtree :(. I have previously reported at least one of these bugs. === In any case, IMO, ido should treat all olpaths as if they were files. Can anybody help track this down? 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] org-mode upgrade and PDF export
The system here is; Ubuntu 12.04LTS, Emacs 23.3.1, Org-mode version 6.33x 1) Emacs with Org was recently installed via the Ubuntu Software Centre. If the Org version here is 6.33x, and Org is now version 8, then I feel I should upgrade Org. The Org Manual http://orgmode.org/manual/Installation.html lists 3 ways to install a new version, but no suggestions how to remove the older version. I can't find an Org 6.3 package in Synaptic to remove. That section warns against have two different versions present. So, I guess it would be best for me to use the first method, "Downloading Org as an archive", and to simply include its load-path in my .emacs. 2) In attempting to publish a sub-section to a PDF, I find I need a pdflatex component and a texi2dvi script. This is referred to Section 8 here; http://orgmode.org/worg/org-tutorials/org-latex-export.html I cannot find pdflatex or texi2dvi in Synaptic, so should I look via apt-get, or are they part of a larger package available to me?
Re: [O] org-mode upgrade and PDF export
On Tue, Aug 27, 2013 at 7:50 PM, adam wrote: > The system here is; Ubuntu 12.04LTS, Emacs 23.3.1, > Org-mode version 6.33x > > 1) > Emacs with Org was recently installed via the Ubuntu Software Centre. > If the Org version here is 6.33x, and Org is now version 8, then I feel > I should upgrade Org. > > The Org Manual http://orgmode.org/manual/Installation.html lists 3 > ways to install a new version, but no suggestions how to remove the > older version. I can't find an Org 6.3 package in Synaptic to remove. > That section warns against have two different versions present. > > So, I guess it would be best for me to use the first method, > "Downloading Org as an archive", and to simply include its load-path > in my .emacs. Correct. You don't have to remove the Org-mode that comes with Emacs via Ubuntu. You just need to download the new archive (or clone with git) and have that in your load path. My setup as the first lines in .emacs: ;; set load paths ;; set load dirs and global config options (add-to-list 'load-path "~/.elisp/org.git/lisp/") (add-to-list 'load-path "~/.elisp/org.git/contrib/lisp") Replace "~/.elisp/org.git/lisp" with wherever you unzip or untar the archive to if you go that route. Just make sure it points to the lisp folder inside the top level folder. > > > 2) > In attempting to publish a sub-section to a PDF, I find I need a > pdflatex component and a texi2dvi script. > This is referred to Section 8 here; > http://orgmode.org/worg/org-tutorials/org-latex-export.html > > I cannot find pdflatex or texi2dvi in Synaptic, so should I look > via apt-get, or are they part of a larger package available to me? > > pdflatex and texi2dvi are provided by a TeX/LaTeX distribution; they are not packages themselves. TexLive is the way most Linux users roll from my experience and reading on the web when I went to install. See this for help: - https://help.ubuntu.com/community/LaTeX >From that article, looks like they may recommend installing directly from TexLive vs. using the Ubuntu package. I used to use Arch Linux's package and then got burned by the annual upgrade as the location of files changes sometimes from year to year and you can end up with a borked system since the package will put LaTeX install files all around your system (/usr/lib, /etc, /usr/local, ...). Now I choose to install by hand via the tl-install script and structure it like this: - System files: ~/.texlive/ (as of now, I have ~/.texlive/2012) - Local stuff: ~/.texlive/texmf-local You can set those quite easily during the tl-install procedure (I chose `tl-install -gui text`). You just change the main TEXDIR option to point where you want it to go. I changed it from /usr/local/texlive/2012 to /home/username/.texlive/2012 and then changed TEXMFLOCAL to /home/username/.texlive/texmf-local. I'm not sure if I customized TEXMFHOME. I don't think I use it and don't have a ~/texmf directory, nor, from looking at my directory structure, something like it inside of one of the other two. Hope that helps! John > >
Re: [O] [PATH] [NEW EXPORTER] two slide backends for contrib
On Tue, Aug 27, 2013 at 10:12 AM, Rick Frankel wrote: > On 2013-08-27 00:41, Matt Price wrote: >> >> I just came across this, having missed it in February. Rick, I was >> wondering if you had thought about enabling some of deck.js's snazzier >> features -- transitions for text elements, for instance, like we see >> in the intro deck here: http://imakewebthings.com/deck.js/#intro >> >> I'm mostly asking because I'd like to try and copy your work to make >> an exporter for impress.js (https://github.com/bartaz/impress.js). >> Kinjo has written one, but it uses the old exporter and no longer >> works with current versions of org, so I thought I would start with >> your deck.js work. >> >> I know that's not very specific, but if you've thought about these >> issues I would love to learn wat you've figured out. Thanks! > > > All the fancy transitions and builds in the deck.js intro are handled > via CSS. So, the exporter will handle them easily. > > If you look at the source for the intro, you will see that all the > builds and transitions are defined in home.css, and applied based on > slide id and/or class. ah, I wish I understood css transforms better! But yes, I can see that they are being defined in home.css and attached to individual classes/ids for slides. That's very helpful. > > If you look at the documentation for ox-deck > @https://github.com/cybercode/org-slides, you will see that you can > specify per-slide classes via the HTML_CONTAINER_CLASS property on the > headline (and any headline can be build by setting the "slide" class > on the headline). ah, I get it now. Thank you. > > Taking a quick look @ the impress.js docs, i noticed that there is an > S9 template for impress.js > (http://slideshow-s9.github.io/slideshow-impress.js), and that > everything is specified w/ slide properties (x, y, z, scale and > rotate), so I would use headline PROPERTIES ( :IMPRESS_X, etc) to > define the slideshow. I'll give that a try, if I end up having time (argh). I'm actually liking deck, though. Am wondering if it would be very hard to add support for the codemirror extension to your deck code. Maybe I'll try that first... > > Also note that it might be easier to inherit from ox-s5 instead of > ox-deck as it is more generic (and add a wrapper around > `org-s5-headline') to process the additional properties. Thanks again, very very helpful. Matt > > rick
Re: [O] faster agenda with properties support disabled (no org-refresh-properties)
Probably the only property most people use most of the time in the agenda is category. Would this get rid of showing category too? 66s to 10s is impressive. I'd give up sorting and selecting category for that. But I wouldn't give up showing category. 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] [bug] g in agenda ignores restriction lock
If I do an agenda with restriction lock set to a subtree, then g, the agenda will ignore the restriction lock. 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.
Re: [O] Has anybody noticed ellipses instead of the top line of the window?
On 4/5/13, Bastien wrote: > It's hard to find reproducible recipes; when we have some (like the > one Brian provided), it's hard to debug; and for I cannot afford to > put this as a priority as the annoyance/hard-to-debug ratio is too > low IMO. > > Let's revive this after 8.0 if needed, Reviving. I provided a recipe in this thread. Here is a fix that sometimes works, but usually not: (defadvice org-optimize-window-after-visibility-change (around fix-recenter activate compile) "fix recenter to be recenter 2 so ellipses do not sometimes show up on line 1. recenter 1 is an emacs bug." (when (get-buffer-window (current-buffer)) (cond ((eq state 'content) nil) ((eq state 'all) nil) ((eq state 'folded) nil) ((eq state 'children) (or (org-subtree-end-visible-p) (recenter 2))) ((eq state 'subtree) (or (org-subtree-end-visible-p) (recenter 2)) -- 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.
