Re: [O] Passing font size to exported LaTeX table
suvayu ali fatkasuvayu+li...@gmail.com writes:
Hello,
On Wed, May 25, 2011 at 12:22 AM, Thomas S. Dye t...@tsdye.com wrote:
#+LaTeX_HEADER: \usepackage{scripttab}
* foo
What's this?
#+tblname: foo
#+CAPTION: foo
| table | here |
|---+--|
| table | here |
What's this?
I think this works OK.
Nick
Aloha Nick,
This works like a charm. Thanks!
Although this is solved now, I found a very simple solution.
e.g. for footnotesize just add the line:
#+ATTR_LaTeX: placement=[options]\footnotesize
Aloha Suvayu,
And this works, too. Thanks!
Can I ask where you found this simple solution?
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
[O] LaTeX export of headings to lists
Hi,
When exporting headings to LaTeX lists, I can see extra vertical blank spaces
if the headings directly starts with a sub-heading or a list. It does not
happen if you have text in your heading (before the sub-heading or the list).
Here's my ECM:
--8---cut here---start-8---
#+OPTIONS: H:2 num:t toc:nil
* Level 1
** Level 2
*** Level 3
A
- A1
- A2
- A3
B
- B1
- B2
- B3
--8---cut here---end---8---
When exporting this example to LaTeX, you can see that there's extra space
between:
- Level 3 and A
- A and A1
- B and B1
This happens beacause the LaTeX export adds and extra line break (\\) after
each \item in addition to the newline (\n). I thus propose the following patch
which fixes the problem:
--8---cut here---start-8---
index 764a48d..706bb4a 100644
--- a/lisp/org-latex.el
+++ b/lisp/org-latex.el
@@ -1234,7 +1234,7 @@ numbered sections and lower levels as unnumbered
sections.
(delete-region (point-at-bol 0) (point))
(insert (format \\begin{%s}\n
(symbol-name org-export-latex-low-levels
-(insert (format \n\\item %s\n%s%%
+(insert (format \n\\item %s\n%s%%
heading
(if label (format \\label{%s} label) )))
(insert (org-export-latex-content content))
--8---cut here---end---8---
If you don't see any problem with this fix, could you apply it?
Thanks a lot,
Francesco Pizzolante
Re: [O] orgmode/beamer - won't export blocks
Benjamin Slade sl...@jnanam.net writes: Thanks, Sebastien and Eric. I updated to org-mode v7.5 [stable], but I'm still having the same problem. I include below a minimal example and also the snippet of code in my .emacs config file which is relevant. Thanks for the example. More importantly, thanks for the snippet of configuration code. The problem, I believe, lies there as your simple file works just fine for me (assuming you have oddeven levels being used; it doesn't work if you have odd only). I would suggest that you no longer need (or want) to customise the org-export-latex-classes variable for beamer. Try removing that customisation, restart emacs and see what happens? HTH. -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1 : using Org-mode version 7.5 (release_7.5.312.gf194)
Re: [O] Passing font size to exported LaTeX table
Hi Tom, On Thu, May 26, 2011 at 11:46 PM, Thomas S. Dye t...@tsdye.com wrote: Although this is solved now, I found a very simple solution. e.g. for footnotesize just add the line: #+ATTR_LaTeX: placement=[options]\footnotesize Aloha Suvayu, And this works, too. Thanks! Can I ask where you found this simple solution? Of course you may. :) I came across a few very nicely written articles by LF Mori in The Practex Journal. This particular solution was discussed in section 3.1 of the following article: http://www.tug.org/pracjourn/2007-1/mori/ HTH -- Suvayu Open source is the future. It sets us free.
Re: [O] [Patch] For the Manual: using org-crypt
Carsten Dominik carsten.domi...@gmail.com writes: Is anyone working on making this a complete patch? Sorry, no. -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
[O] org-capture in the same file from which it was called under certain heading
Hi I would like to capture todo items, changes and other things in the file I am working in (literate programming), but I am struggling: how can I specify thet the file is the actual file I am working in? Thanks, Rainer -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax (F): +33 - (0)9 58 10 27 44 Fax (D):+49 - (0)3 21 21 25 22 44 email: rai...@krugs.de Skype: RMkrug
Re: [O] [Patch] For the Manual: using org-crypt
On 27/05/11 10:15, Christian Egli wrote: Carsten Dominikcarsten.domi...@gmail.com writes: Is anyone working on making this a complete patch? Sorry, no. I'll have a go and try to make a proper patch against the current manual. Don't blame me if the manual breaks:) Ian.
[O] Semantics of 'C-c -' and massively-indented lists
Hello, I'm a beginner, so please let me know if I'm completely off the mark. The effects of converting from headline to list with 'C-c -' and back to 'C-c *' don't behave as I'd expect. The indentation levels seem all wrong, no matter how you look at it. My Setup I'm using org 7.5 with Cocoa emacs 23.3 on OSX Note that I do not have the odd option on, I don't do visual-line-mode, and I rely on org-adapt-indentation to be on. Converting from headline to list If I have a LEVEL=5 headline and I convert it to a list with 'C-c -', I get too much indentation * Headline * Converted Line becomes * Headline - Converted Line After looking at the code, I have the impression that the intent is that the LEVEL of the line should remain 5; thus, the list is indented by 2 spaces for each level under 5, i.e. 8 spaces. But who needs a LEVEL=5 list at this point? Expected behavior ~ What I would like is a LEVEL=1 list, properly indented along with the rest of the body text. If org-adapt-indentation is t, then I would expect to see: * Headline - Converted Line where the '-' is aligned with the 'H' of the above headline, at the same column where any body text would start if I hit TAB in a line after Headline (if there were no list). And if org-adapt-indentation is nil, then I would expect to see: * Headline - Converted Line Workaround ~~ Right now, what I have to do is manuallay remove the extra spaces to do the alignment myself. Converting from list to headline In fact, if I take the list and I try to convert it back to a headline with 'C-c *', it doesn't even matter how many spaces there are in front of the '-': it's always converted to a LEVEL=5 headline because the parent is LEVEL=4: * Headline - Converted Line becomes * Headline ** Converted Line * Headline - Converted Line also becomes * Headline ** Converted Line * Headline - Converted Line also becomes * Headline ** Converted Line Well, at least 'C-c *' acts the way I'd expect it to: the line becomes a sub-heading of Headline. Other modes ~~~ Things look especially weird when org-indent-mode is turned on, since you have a mixture of visual indentation and hard space indentation. I would expect a 'C-c -' to insert no hard spaces at all and leave everything in column 0 and let the visual-line-mode adjust the display. If you have 'odd' mode on, however, everything seems to look perfectly. Why? Sheer luck and maybe an off-by-1 bug. The headlines go up by 2 columns, and '- ' also happens to be 2 characters long. But also, if 'odd' mode is on, for some reason 1 is added to the resulting list level. So after the conversion, the list just happens to lign up perfectly with the 'H' of Headline. * Headline LEVEL=3 * Converted Line LEVEL=3 becomes * Headline LEVEL=3 - Converted Line LEVEL=4 This might be the reason that some people haven't noticed this problem. Maybe most users use 'odd' mode? Acting relative to the parent ~ Now, what happens when we convert the previous example back by using 'C-c *'? We get a LEVEL-4 headline. * Headline LEVEL=3 - Converted Line LEVEL=4 becomes * Headline LEVEL=3 *** Converted Line LEVEL=4 The operations are not symmetric because somehow the LEVEL was incremented. Well, this behavior actually makes sense. When we converted from headline to list, we were saying that the headline should now be part of the body text of Headline, so it should be considered a child of Headline, i.e. LEVEL=4. And going back, well, we might as well preserve LEVEL=4, keeping it as a child of Headline, instead of guessing the user's intent to be LEVEL=3, a sibling of Headline. What doesn't make sense is what happens when do 'C-c -' once again. * Headline LEVEL=3 *** Converted Line LEVEL=4 becomes * Headline LEVEL=3 - Converted Line LEVEL=5 Whoa, all we did was 'C-c -' then 'C-c *' then 'C-c -' and the line got demoted. I bet at this time, you'd like to know what hapepns when you hit 'C-c *'. Don't worry, I did it for you. It comes back to LEVEL=4. It actually stabilizes, thank god. * Headline LEVEL=3 - Converted Line LEVEL=5 becomes * Headline LEVEL=3 *** Converted Line LEVEL=4 Expected behavior ~ For a given parent headline, there are several cases when applying 'C-c -'. 1) * Headline LEVEL=3 * Converted Line LEVEL=3 2) * Headline LEVEL=3 *** Converted Line LEVEL=4 3) * Headline LEVEL=3 * Converted Line LEVEL=5 4) * Headline LEVEL=3 *** Converted Line LEVEL=2 For any case, the resulting list should just be a LEVEL=1 list regardless of the level that it started, and it should be properly indented according to the parent headline. That's because a list
[O] [PATCH] Implement priority inheritance for agenda views.
* lisp/org.el (org-use-prio-inheritance): New customizable for using priority inheritance in agenda views. Defaults to off (org-get-priority-char): Factored out from org-get-priority. Return priority token from headline, defaulting to an optional fallback or org-default-priority. (org-get-priority): Use org-get-priority-char. Default to an optional fallback or org-default-priority. (org-scan-tags): Assign and display priority according to org-use-prio-inheritance. --- This patch can be pulled from branch prio-inherit at git://github.com/altruizine/org-mode.git . I am aware that priority inheritance for to-do items has been requested and rejected in the past, on the grounds of inherited priorities allegedly inflating the number of assigned priorities, thereby defeating the purpose of priorities. Well, I disagree, as I have found inherited priorities useful in practice. The code changes are relatively minor, with explicit tracking of the priority tag for each level, and pasting in this tag into the agenda items when the inherited priority differs from the default priority. Comments welcome! Michael PS: An FSF copyright-assignment process is in progress. lisp/org.el | 55 +++ 1 files changed, 43 insertions(+), 12 deletions(-) diff --git a/lisp/org.el b/lisp/org.el index cdf48c1..72a23f7 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -2498,6 +2498,14 @@ command used) one higher or lower that the default priority. :group 'org-priorities :type 'boolean) +(defcustom org-use-prio-inheritance nil + Non-nil means priority in levels apply also for sublevels. +When nil, only the priority directly given in a specific line apply there. + :group 'org-priorities + :type '(choice + (const :tag Not nil) + (const :tag Always t))) + (defcustom org-get-priority-function nil Function to extract the priority from a string. The string is normally the headline. If this is nil Org computes the @@ -12332,15 +12340,20 @@ ACTION can be `set', `up', `down', or a character. (message Priority removed) (message Priority of current item set to %s news -(defun org-get-priority (s) - Find priority cookie and return priority. +(defun org-get-priority-char (s optional fallback) + Return priority cookie as char. Defaults to FALLBACK or, if that's +unset, to org-default-priority. + (save-match-data +(if (string-match org-priority-regexp s) + (string-to-char (match-string 2 s)) + (or fallback org-default-priority + +(defun org-get-priority (s optional fallback) + Find priority cookie and return priority. Defaults to FALLBACK or, if that's +unset, to org-default-priority. (if (functionp org-get-priority-function) (funcall org-get-priority-function) -(save-match-data - (if (not (string-match org-priority-regexp s)) - (* 1000 (- org-lowest-priority org-default-priority)) - (* 1000 (- org-lowest-priority - (string-to-char (match-string 2 s +(* 1000 (- org-lowest-priority (org-get-priority-char s fallback) Tags @@ -12393,8 +12406,9 @@ only lines with a TODO keyword are included in the output. (org-map-continue-from nil) lspos tags tags-list (tags-alist (list (cons 0 org-file-tags))) +(prio-alist (list (cons 0 org-default-priority))) (llast 0) rtn rtn1 level category i txt -todo marker entry priority) +todo marker entry priority prio-char) (when (not (or (member action '(agenda sparse-tree)) (functionp action))) (setq action (list 'lambda nil action))) (save-excursion @@ -12409,8 +12423,18 @@ only lines with a TODO keyword are included in the output. (goto-char (setq lspos (match-beginning 0))) (setq level (org-reduced-level (funcall outline-level)) category (org-get-category)) - (setq i llast llast level) + (setq txt (org-get-heading)) + + (when org-use-prio-inheritance + ;; remove prio from same and sublevels + (while (= (caar prio-alist) level) + (pop prio-alist)) + ;; add this prio + (setq prio-char (org-get-priority-char txt (cdar prio-alist))) + (push (cons level prio-char) prio-alist)) + ;; remove tag lists from same and sublevels + (setq i llast llast level) (while (= i level) (when (setq entry (assoc i tags-alist)) (setq tags-alist (delete entry tags-alist))) @@ -12469,21 +12493,28 @@ only lines with a TODO keyword are included in the output. (cond ((eq action 'sparse-tree) (and org-highlight-sparse-tree-matches - (org-get-heading) (match-end 0) + txt (match-end 0) (org-highlight-new-match (match-beginning 0) (match-beginning 1))) (org-show-context
[O] Org mode comment
Hello, Just started using org-mode and I love it already. The export to LaTeX feature is fantastic. Thanks for the great work! Alan.
[O] Bug: org-entities iuml correction [7.01trans]
Hi,
Just a minor bug concerning latex and a special character.
The org-entities entry for iuml is currently: (still there in v. 7.5,
by the way)
(iuml \\\{i} nil iuml; i ï ï)
Imho, it should be:
(iuml \i{} nil iuml; i ï ï)
Note the escaping of the i in the latex string. The original version will cause
the i to have three dots (which is incorrect). Escaping the i will suppress the
dot from the original character, so that the resulting output from latex will
have two dots.
Emacs : GNU Emacs 23.1.1 (i386-apple-darwin9.8.0, NS apple-appkit-949.54)
of 2009-08-16 on black.local
Package: Org-mode version 7.01trans
[O] having problems this mailing list configuration
Hi all. I have some problems with mailing list configuration. I wanted to disable mail delivery and check list via web interface, but some how it goes not save the changes I make. I have enabled cookies dan it workd with other mailing lists. Thanks for help in advance. Petro
[O] Assets Packing
Hi all, Maybe this already exists in org, but I needed a function that looks at all the image links, signals if the link is broken or not, copies the files into a folder and relinks it. Comments and crits are greatly appreciated, I started coding elisp 2 weeks ago, so any and all pointers and tips are welcome. ---8- cut here (defcustom sndr-assets-dir nil the directory org linked assets are moved to, do not forget trailing slash... :type '(string) :group'sndr ) (defun sndr-assets-package() finds file links and moves them to a dir specified, or ./assets , relative to the org file (interactive) (let (p0 p1) (save-excursion (goto-char (point-min)) (while (search-forward-regexp \\[\\[\\([^][]+\\)\\]\\(\\[\\([^][]+\\)\\]\\)?\\] nil t) (match-beginning 1) (setq p0 (match-beginning 1)) (setq p1 (match-end 1)) (sndr-link-check-and-move p0 p1) ) ))) (defun sndr-link-check-and-move (p0 p1) gets a buffer section, checks if it is a file, moves the file to a dir specified (or ./assets) and updates the buffer accordingly (let (file newdir newfile) (setq file (buffer-substring-no-properties p0 p1 )) (file-exists-p file) (setq newdir (or sndr-assets-dir (concat (file-name-directory buffer-file-name) assets/))) (setq newfile (concat newdir(file-name-nondirectory file))) (if (not (file-exists-p newdir)) (make-directory newdir t)) (if (file-exists-p file) (progn (if (not(file-exists-p newfile)) (copy-file file newfile)) (goto-char p0) (delete-region p0 p1) (insert newfile) ) (progn (goto-char p0) (delete-region p0 p1) (insert (concat BROKEN# file #BROKEN)) ---8- cut here sander.
Re: [O] [bug, babel] export corruption bug and 3 more bugs
Hi David, Thank you. I am unable to debug this further so I appreciate it. Is it necessary to construct this regexp for babel if babel is not used? Were you able to reproduce the corruption bug? Did anybody else? Emacs -Q, minimal test case. (I'm trying to warn the world about one definitely-already-existing global pandemic of an AIDS-like disease that nobody has heard of but is 2x the size of AIDS in the USA -- and a possible global pandemic 10x the size of HIV -- but my normally-sublimely-excellent software is dropping random lines. :/ Hmm, should I switch to talking about Justin Bieber and use Microsoft Word instead? :) We could hand out soma with Word and tell people it's just as good as Org. :)) Samuel P.S. Please feel free to put the compatibility fixes into org-compat or wherever. -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com I support the Whittemore-Peterson Institute (WPI) === I want to see the original (pre-hold) Lo et al. 2010 NIH/FDA/Harvard MRV paper.
Re: [O] [bug, babel][OT] export corruption bug and 3 more bugs
(I'm trying to warn the world about one definitely-already-existing global pandemic of an AIDS-like disease that nobody has heard of but is 2x the size of AIDS in the USA -- and a possible global pandemic 10x the size of HIV -- but my normally-sublimely-excellent software is dropping random lines. :/ Hmm, should I switch to talking about Justin Bieber and use Microsoft Word instead? :) We could hand out soma with Word and tell people it's just as good as Org. :)) That's LOTS of keystrokes. Jambunathan K. --
Re: [O] Incorrect LaTex Export
Hello,
Jai Bharat Patel i...@jaib.net writes:
The following fragment(in minimal.org) used to work correctly with
org-mode-7.3 when exporting to pdf (C-c C-e d), but not working with latest
code in the latest snapshot
#+TITLE:
#+AUTHOR:
#+EMAIL:
#+DATE:
#+OPTIONS: toc:nil ^:nil
#+LATEX_HEADER: \usepackage{listings,babel}
#+LATEX_HEADER: \lstset{breaklines=true, basicstyle=\ttfamily,
frame=shadowbox}
#+BEGIN_LaTeX
\begin{lstlisting}
--
Item List:
--
- Item 1
- Item 2
- Item 3
\end{lstlisting}
#+END_LaTeX
This should now be fixed in master. Don't hesitate to report back if it
isn't. Thanks for reporting this !
Regards,
--
Nicolas Goaziou
Re: [O] [bug, babel][OT] export corruption bug and 3 more bugs
On 2011-05-27, Jambunathan K kjambunat...@gmail.com wrote: That's LOTS of keystrokes. You don't know all the facts.
Re: [O] [bug, babel][OT] export corruption bug and 3 more bugs
What are you saying? --
Re: [O] [Babel][Bug] Inconsistent output from babel function depending on how called
Ethan Ligon li...@are.berkeley.edu writes: On Thu, May 26, 2011 at 12:17 PM, Christian Moe m...@christianmoe.com wrote: No, this is expected (if possibly under-documented behavior). The :results header arguments are associated with the code block and *not* with the #+call line. To get the desired behavior, you must specify the :results header argument on the #+call: line thusly. #+call: print_list(lst=list1) :results output org Best -- Eric Hi, I recently made the same mistake, and it took me a while to figure things out. I had assumed #+CALLs inherited all the header arguments from the code blocks they referenced. Regarding documentation, I see now that the correct behavior is at least implicitly documented in the first example at [[info:org#Header%20arguments%20in%20function%20calls]]. It might rate an explicit explanation at [[info:org#Evaluating%20code%20blocks]] as well, though. I'd be happy to help with the documentation, but I still don't understand the behavior. It seems as though some arguments to :results need to be supplied to the code block, but others have to be supplied to the call. In my situation, the org option to :results has to be supplied to the call, while the output option has to be supplied to the code block. What's the logic? Here's my setup: #+results: list1 - Item1 - Item2 #+results: list2 - Item3 - Item4 #+source: print_list(lst) #+begin_src sh for i in $lst; do echo * $i done #+end_src Here's a way of calling that works #+call: print_list[:results output](lst=list1) :results org #+results: print_list[:results output](lst=list1) #+BEGIN_ORG * Item1 * Item2 #+END_ORG but this way of calling doesn't #+call: print_list[:results output org](lst=list2) #+results: print_list[:results output org](lst=list2) : * Item3 : * Item4 and neither does this way #+call: print_list[:results org](lst=list2) :results output #+results: print_list[:results org](lst=list2) or this way #+call: print_list(lst=list2) :results output org #+results: print_list(lst=list2) #+END_ORG #+BEGIN_ORG Thanks for any enlightenment! -Ethan Hi Ethan, There are two different places for specifying header argument in a #+call line, these places are marked with and in the following, both are optional... #+call: code_bloc_name[](arguments) Header arguments located in these two locations are treated differently. - :: Those placed in the location are passed through and applied to the code block being called. These header arguments affect how the code block is evaluated, for example [:results output] will collect the results from STDOUT of the called code block. - :: Those placed in the location are applied to the call line and do not affect the code block being called. These header arguments affect how the results are incorporated into the Org-mode buffer when the #+call line is evaluated, and how the #+call line is exported. For example :results org at the end of the call line will insert the results of the call line in an Org-mode block. Is this more clear? Is there a way it can be made more straightforward? If the above seems reasonable then I can add it to the documentation. Thanks -- Eric
Re: [O] [Babel][Bug] Inconsistent output from babel function depending on how called
Ethan Ligon li...@are.berkeley.edu writes: So, the :result output org ought to be associated with the *call*, not with the function. That makes good sense. But perhaps it still doesn't work quite as it ought... On Thu, May 26, 2011 at 11:46 AM, Eric Schulte schulte.e...@gmail.com wrote: Ethan Ligon li...@are.berkeley.edu writes: I'd like to call a simple babel code block to generate org-code If I define a list thusly: #+results: list1 - foo - bar Then I define a code block thusly, and execute it by C-c C-c on the source line. That yields the desired result: a sequence of headings under #+results: print_list. #+source: print_list(lst=list1) #+begin_src sh :results output org for i in $lst; do echo * $i done #+end_src #+results: print_list #+BEGIN_ORG * foo * bar #+END_ORG Now I want to reuse the code block to generate other sequences of headings. But even if I call it with the *same* list, instead of the desired headings, I get a literal, as below. #+call: print_list(lst=list1) #+results: print_list(lst=list1) : * foo : * bar I think this qualifies as a bug---surely the method of calling the code block shouldn't affect the output? No, this is expected (if possibly under-documented behavior). The :results header arguments are associated with the code block and *not* with the #+call line. To get the desired behavior, you must specify the :results header argument on the #+call: line thusly. #+call: print_list(lst=list1) :results output org If I do this, I get #+results: print_list(lst=list1) #+END_ORG #+BEGIN_ORG which is surprising first because there's no proper output, but also because the end and begin tags are reversed (!). What *does* work is to omit the output header argument. #+call: print_list(lst=list1) :results org #+results: print_list(lst=list1) #+BEGIN_ORG * foo * bar #+END_ORG So now I definitely have a good work-around, but still think there's a bug. Well yes and no... There is a bug here, but not in the interpretation of the header arguments... the interpretation is just so non-intuitive that I also misunderstood the resulting behavior in my earlier reply. In the example of #+call: print_list(lst=list1) :results output org both the org and output header arguments are applied to the call line, when in fact the output header argument should be applied to the list1 code block (not the call line). The results of applying the output header argument to the call line is to return no results (which makes sense because the call line does not print to STDOUT). The correct form of the above would be as follows (explicitly passing the output header argument to the list1 code block) #+call: list1[:results output](lst=~/Desktop) :results org #+results: list1[:results output](lst=~/Desktop) #+BEGIN_ORG * ~/Desktop #+END_ORG There is an error however in that when no results are returned the begin/end parts of the Org-mode code block are flipped... Thanks, -Ethan -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] Passing font size to exported LaTeX table
suvayu ali fatkasuvayu+li...@gmail.com writes: Hi Tom, On Thu, May 26, 2011 at 11:46 PM, Thomas S. Dye t...@tsdye.com wrote: Although this is solved now, I found a very simple solution. e.g. for footnotesize just add the line: #+ATTR_LaTeX: placement=[options]\footnotesize Aloha Suvayu, And this works, too. Thanks! Can I ask where you found this simple solution? Of course you may. :) I came across a few very nicely written articles by LF Mori in The Practex Journal. This particular solution was discussed in section 3.1 of the following article: http://www.tug.org/pracjourn/2007-1/mori/ HTH Aloha Suvayu, Thank you for the link to the Mori article. It is nicely written. My question was poorly written, though. I'm interested to know where you found the Org-mode line: #+ATTR_LaTeX: placement=[options]\footnotesize I haven't been able to find this solution anywhere else. All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] [Babel][Bug] Inconsistent output from babel function depending on how called
Christian Moe m...@christianmoe.com writes: No, this is expected (if possibly under-documented behavior). The :results header arguments are associated with the code block and *not* with the #+call line. To get the desired behavior, you must specify the :results header argument on the #+call: line thusly. #+call: print_list(lst=list1) :results output org Best -- Eric Hi, I recently made the same mistake, and it took me a while to figure things out. I had assumed #+CALLs inherited all the header arguments from the code blocks they referenced. Regarding documentation, I see now that the correct behavior is at least implicitly documented in the first example at [[info:org#Header%20arguments%20in%20function%20calls]]. It might rate an explicit explanation at [[info:org#Evaluating%20code%20blocks]] as well, though. Yours, Christian I've just updated the documentation at the following to reflect the full range of #+call line header argument options. #+begin_src emacs-lisp (info (org)Evaluating code blocks) #+end_src Thanks for the recommendation -- Eric -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] Passing font size to exported LaTeX table
Hello Tom, On Fri, 27 May 2011 06:17:04 -1000 t...@tsdye.com (Thomas S. Dye) wrote: Aloha Suvayu, Thank you for the link to the Mori article. It is nicely written. My question was poorly written, though. I'm interested to know where you found the Org-mode line: #+ATTR_LaTeX: placement=[options]\footnotesize I haven't been able to find this solution anywhere else. I got the solution by reading between the lines and some experimentation. The placement option is documented in the section referenced below[1]. Note that this does not say anything about tables. I think I found it by experimenting that this also works for tables. When I saw the LaTeX solution in the article I mentioned earlier, I tried out and found exporting as above works. :) All the best, Tom HTH Footnotes: [1] http://orgmode.org/manual/Images-in-LaTeX-export.html#Images-in-LaTeX-export -- Suvayu Open source is the future. It sets us free.
Re: [O] orgmode/beamer - won't export blocks
Thank you for the help. Yes, removing the configuration code from .emacs results in the correct behaviour (i.e. blocks are now exported properly). Quick question -- is there still a way of setting up beamer/orgmode configuration in .emacs? thanks, --Ben On 27 May 2011 02:01, Eric S Fraga e.fr...@ucl.ac.uk wrote: Benjamin Slade sl...@jnanam.net writes: Thanks, Sebastien and Eric. I updated to org-mode v7.5 [stable], but I'm still having the same problem. I include below a minimal example and also the snippet of code in my .emacs config file which is relevant. Thanks for the example. More importantly, thanks for the snippet of configuration code. The problem, I believe, lies there as your simple file works just fine for me (assuming you have oddeven levels being used; it doesn't work if you have odd only). I would suggest that you no longer need (or want) to customise the org-export-latex-classes variable for beamer. Try removing that customisation, restart emacs and see what happens? HTH. -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1 : using Org-mode version 7.5 (release_7.5.312.gf194)
Re: [O] Problem with make and autoloads
Matt Lundin m...@imapmail.org writes: The autoloads in org-install all have lisp/ prepended to the file name. What is prefix and lispdir set to in the Makefile? Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] Passing font size to exported LaTeX table
Suvayu Ali fatkasuvayu+li...@gmail.com writes: Hello Tom, On Fri, 27 May 2011 06:17:04 -1000 t...@tsdye.com (Thomas S. Dye) wrote: Aloha Suvayu, Thank you for the link to the Mori article. It is nicely written. My question was poorly written, though. I'm interested to know where you found the Org-mode line: #+ATTR_LaTeX: placement=[options]\footnotesize I haven't been able to find this solution anywhere else. I got the solution by reading between the lines and some experimentation. The placement option is documented in the section referenced below[1]. Note that this does not say anything about tables. I think I found it by experimenting that this also works for tables. When I saw the LaTeX solution in the article I mentioned earlier, I tried out and found exporting as above works. :) All the best, Tom HTH Footnotes: [1] http://orgmode.org/manual/Images-in-LaTeX-export.html#Images-in-LaTeX-export Aloha Suvayu, I think #+ATTR_LaTeX: needs more documentation. I worked very hard to read between the lines of the Org-mode manual to arrive at your simple solution but didn't manage to come close! Are you able to summarize the possibilities of #+ATTR_LaTeX? I'm thinking that a general description somewhere in the Org-mode manual might be useful. It would probably also be good to augment the existing descriptions of its use in the manual, as well. Perhaps it would be possible to propose a patch to the documentation? All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] Passing font size to exported LaTeX table
Hello Tom,
On Fri, 27 May 2011 07:37:50 -1000
t...@tsdye.com (Thomas S. Dye) wrote:
Aloha Suvayu,
I think #+ATTR_LaTeX: needs more documentation. I worked very hard to
read between the lines of the Org-mode manual to arrive at your simple
solution but didn't manage to come close!
Are you able to summarize the possibilities of #+ATTR_LaTeX? I'm
thinking that a general description somewhere in the Org-mode manual
might be useful. It would probably also be good to augment the
existing descriptions of its use in the manual, as well. Perhaps it
would be possible to propose a patch to the documentation?
I am not very familiar with org-latex internals. Based on my limited
understanding I wrote the attached patch to the org manual. I hope it
is up to par.
All the best,
Tom
Thanks a lot for your encouragement. :)
--
Suvayu
Open source is the future. It sets us free.
From 431d7e275a0b374c7b1e8135fe7e5c7d72f46a75 Mon Sep 17 00:00:00 2001
From: Suvayu Ali fatkasuvayu+li...@gmail.com
Date: Fri, 27 May 2011 11:18:35 -0700
Subject: [PATCH] Documentation on placement options in LaTeX export.
* Placement options can be passed to floating environments
like 'figure' or 'table' with the '#+ATTR_LaTeX:' line
during LaTeX export. Added an example to demonstrate that.
---
doc/org.texi | 17 +++--
1 files changed, 15 insertions(+), 2 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index aa34cd3..5fa1e22 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -10160,7 +10160,7 @@ All lines between these markers are exported literally
@subsection Tables in @LaTeX{} export
@cindex tables, in @LaTeX{} export
-For @LaTeX{} export of a table, you can specify a label and a caption
+For @LaTeX{} export of a table, you can specify a label, a caption and
placement options
(@pxref{Images and tables}). You can also use the @code{ATTR_LaTeX} line to
request a @code{longtable} environment for the table, so that it may span
several pages, or to change the default table environment from @code{table}
@@ -10207,7 +10207,20 @@ element. You can use an @code{#+ATTR_LaTeX:} line to
specify the various
options that can be used in the optional argument of the
@code{\includegraphics} macro. To modify the placement option of the
@code{figure} environment, add something like @samp{placement=[h!]} to the
-Attributes.
+Attributes. It is to be noted this option can be used with tables as well.
+The options are passed as the placement option to floating environments like
+@code{figure} or @code{table}. One can pass other compatible options as well.
+For example the @code{#+ATTR_LaTeX:} line below is exported as the
+@code{figure} environment below it.
+
+@cindex #+ATTR_LaTeX
+@example
+#+ATTR_LaTeX: placement=[options]\footnotesize
+
+\begin{figure}[options]\footnotesize
+...
+\end{figure}
+@end example
If you would like to let text flow around the image, add the word @samp{wrap}
to the @code{#+ATTR_LaTeX:} line, which will make the figure occupy the left
--
1.7.5.1
Re: [O] Passing font size to exported LaTeX table
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
Hello Tom,
On Fri, 27 May 2011 07:37:50 -1000
t...@tsdye.com (Thomas S. Dye) wrote:
Aloha Suvayu,
I think #+ATTR_LaTeX: needs more documentation. I worked very hard to
read between the lines of the Org-mode manual to arrive at your simple
solution but didn't manage to come close!
Are you able to summarize the possibilities of #+ATTR_LaTeX? I'm
thinking that a general description somewhere in the Org-mode manual
might be useful. It would probably also be good to augment the
existing descriptions of its use in the manual, as well. Perhaps it
would be possible to propose a patch to the documentation?
I am not very familiar with org-latex internals. Based on my limited
understanding I wrote the attached patch to the org manual. I hope it
is up to par.
All the best,
Tom
Thanks a lot for your encouragement. :)
--
Suvayu
Open source is the future. It sets us free.
From 431d7e275a0b374c7b1e8135fe7e5c7d72f46a75 Mon Sep 17 00:00:00 2001
From: Suvayu Ali fatkasuvayu+li...@gmail.com
Date: Fri, 27 May 2011 11:18:35 -0700
Subject: [PATCH] Documentation on placement options in LaTeX export.
* Placement options can be passed to floating environments
like 'figure' or 'table' with the '#+ATTR_LaTeX:' line
during LaTeX export. Added an example to demonstrate that.
---
doc/org.texi | 17 +++--
1 files changed, 15 insertions(+), 2 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index aa34cd3..5fa1e22 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -10160,7 +10160,7 @@ All lines between these markers are exported literally
@subsection Tables in @LaTeX{} export
@cindex tables, in @LaTeX{} export
-For @LaTeX{} export of a table, you can specify a label and a caption
+For @LaTeX{} export of a table, you can specify a label, a caption and
placement options
(@pxref{Images and tables}). You can also use the @code{ATTR_LaTeX} line to
request a @code{longtable} environment for the table, so that it may span
several pages, or to change the default table environment from @code{table}
@@ -10207,7 +10207,20 @@ element. You can use an @code{#+ATTR_LaTeX:} line
to specify the various
options that can be used in the optional argument of the
@code{\includegraphics} macro. To modify the placement option of the
@code{figure} environment, add something like @samp{placement=[h!]} to the
-Attributes.
+Attributes. It is to be noted this option can be used with tables as well.
+The options are passed as the placement option to floating environments like
+@code{figure} or @code{table}. One can pass other compatible options as well.
+For example the @code{#+ATTR_LaTeX:} line below is exported as the
+@code{figure} environment below it.
+
+@cindex #+ATTR_LaTeX
+@example
+#+ATTR_LaTeX: placement=[options]\footnotesize
+
+\begin{figure}[options]\footnotesize
+...
+\end{figure}
+@end example
If you would like to let text flow around the image, add the word @samp{wrap}
to the @code{#+ATTR_LaTeX:} line, which will make the figure occupy the left
Aloha Suvayu,
This looks like an improvement to me. I'd be interested to hear what
Nick and Seb might have to say. They often catch things I miss.
If you don't get other comments, I'd encourage you to submit this as a
patch (I think this requires [PATCH] in the subject line) to see what
Carsten and crew have to say about it.
Thanks again for finding this solution to specifying the font size for
floating tables on a table-by-table basis in LaTeX export. I'd been
looking for your solution, and for Nick's solution that works on a
per-document or buffer basis, for many months without success.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Re: [O] orgmode/beamer - won't export blocks
Hi Benjamin,
Benjamin Slade wrote:
Thank you for the help.
Yes, removing the configuration code from .emacs results in the
correct behaviour (i.e. blocks are now exported properly).
Where did you find that way to do? I guess in old threads... Is it still on
Worg, this should be removed.
Quick question -- is there still a way of setting up beamer/orgmode
configuration in .emacs?
Why are you asking that? It's even better: you don't need any special
configuration anymore (like before) for beamer to work out of the box.
The only lines I still have in my .emacs about beamer are:
#+begin_src emacs-lisp
;; XXX 2010-03-25 TEMP Fix for conflict TikZ/hyperref: loading
;; `atbegshi' before document class beamer
(add-to-list 'org-export-latex-classes
'(beamer
\\RequirePackage{atbegshi}
\\documentclass{beamer}\n
org-beamer-sectioning))
#+end_src
Maybe even not needed anymore...
Best regards,
Seb
--
Sébastien Vauban
Re: [O] Completing with anything
With these two modifications, it runs fine (that is, using the old calling convention and just using (setq-default completion-at-point-functions '(my-dabbrev-expand))) Thanks, installed, Stefan
