Re: [O] LaTeX export TOC decorations : how to
FAb <0x...@free.fr> writes:
> Hi,
> When I org-export in pdf the items in TOC have red box around them like
> "decoration" for link in css.
> How can I get ride of them ?
> Or how to customize this stuff ?
The boxes come from the default setup of hyperref in LaTeX and the
behavior can be customized via ~\hypersetup{}~. Here is an example on a
file basis that changes the link identification from a box to a text
color (~colorlinks=true~) and then specifies the particular color
(~linkcolor=blue~):
#+LaTeX_HEADER: \hypersetup{colorlinks=true, linkcolor=blue}
Refer to the Extension Options of the hyperref manual[fn:1] for more
details and possibilities.
[fn:1] http://mirror.unl.edu/ctan/macros/latex/contrib/hyperref/doc/manual.pdf
>
> Thanks
>
>
--
Tim Burt
www.rketburt.org
"It is healthful to every sane man to utter the art within him;" -- GK
Chesterton
Re: [O] [PATCH] datetree: Recognize year headline with tags as a match
Jeffrey Brent McBeth writes: > On Mon, Feb 25, 2013 at 10:48:16AM +0100, Bastien wrote: >> Hi Tim, >> >> Tim Burt writes: >> >> > * lisp/org-datetree.el (org-datetree-find-year-create): >> > Include regexp for tags. Syntax was taken directly >> > from org-todo-line-tags-regexp in org.el. >> >> Applied, thanks a lot for the patch and the detailed change log! >> >> Best, > > I can confirm that latest git fixes my use case. Thank you both so much. Excellent all the way 'round. > > Jeff -- Tim Burt www.rketburt.org "It is healthful to every sane man to utter the art within him;" -- GK Chesterton
Re: [O] org-capture, datetree, and tags
I have just submitted a patch. It is marked with TINYCHANGE so that it can be processed before the assignment paperwork (which I just began today) is complete. Good day, Tim Tim Burt writes: > Bastien writes: > >> Hi Tim, >> >> Tim Burt writes: >> >>> : (defun org-datetree-find-year-create (year) >>> :(let ((re "^\\*+[ \t]+\\([12][0-9][0-9][0-9]\\)[ >>> \t]*\\(:[[:alnum:]_@]*\\)*:*[ \t]*$") >>> : match) >>> I've tested with the following headlines: >>> - 2013 >>>- both with and without trailing spaces >>> - 2013 :abc: >>> - 2013 :abc123: >>> - 2013 :abc123:_underscore:@attaboy:: >>> - 2013 :noexport: >>> >>> Any comments on the regular expression are welcome before I make >>> patch. >> >> Thanks for working on fixing this. >> >> The more or less standard regexp for tags-till-end-of-line is this: >> >>:[[:alnum:]_@#%:]*[ \t]*$ >> ^ >> >> With * if you want to match headlines with no tag. > > I may have misapplied what you suggested, but the new regexp (see below) > does not work on a year headline without tags. > : (defun org-datetree-find-year-create (year) > :(let ((re "^\\*+[ \t]+\\([12][0-9][0-9][0-9]\\)[ > \t]*\\(:[[:alnum:]_@#%:]*[ \t]*$\\)") > : match) > However, the suggestion helped me find the following in > org-todo-line-tags-regexp > \\(.*?\\([ \t]:[[:alnum:]:_@#%]+:[ \t]*\\)?$\\) > Applying this regexp worked on a tag-free headline (both with and > without trailing spaces) > : (defun org-datetree-find-year-create (year) > :(let ((re "^\\*+[ \t]+\\([12][0-9][0-9][0-9]\\)\\(.*?\\([ > \t]:[[:alnum:]:_@#%]+:[ \t]*\\)?$\\)") > : match) > > > >> >> Please have a look at this page before submitting a patch: >> http://orgmode.org/worg/org-contribute.html#sec-5 > > Will do. > >> >> Thanks! -- Tim Burt www.rketburt.org "It is healthful to every sane man to utter the art within him;" -- GK Chesterton
[O] [PATCH] datetree: Recognize year headline with tags as a match
* lisp/org-datetree.el (org-datetree-find-year-create): Include regexp for tags. Syntax was taken directly from org-todo-line-tags-regexp in org.el. Change made to fix the problem where a year headline of a datetree was not matched if it had a tag. The :NOEXPORT: tag is one useful case that should be matched. Initial problem observation reported by Jeffrey McBeth on the org-mode mailing list. TINYCHANGE --- lisp/org-datetree.el | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lisp/org-datetree.el b/lisp/org-datetree.el index f2e35fa..0102393 100644 --- a/lisp/org-datetree.el +++ b/lisp/org-datetree.el @@ -72,7 +72,7 @@ tree can be found." (goto-char (prog1 (point) (widen)) (defun org-datetree-find-year-create (year) - (let ((re "^\\*+[ \t]+\\([12][0-9][0-9][0-9]\\)\\s-*$") + (let ((re "^\\*+[ \t]+\\([12][0-9][0-9][0-9]\\)\\(.*?\\([ \t]:[[:alnum:]:_@#%]+:\\)?\\s-*$\\)") match) (goto-char (point-min)) (while (and (setq match (re-search-forward re nil t)) -- 1.7.11.7
Re: [O] org-capture, datetree, and tags
Bastien writes: > Hi Tim, > > Tim Burt writes: > >> : (defun org-datetree-find-year-create (year) >> :(let ((re "^\\*+[ \t]+\\([12][0-9][0-9][0-9]\\)[ >> \t]*\\(:[[:alnum:]_@]*\\)*:*[ \t]*$") >> : match) >> I've tested with the following headlines: >> - 2013 >>- both with and without trailing spaces >> - 2013 :abc: >> - 2013 :abc123: >> - 2013 :abc123:_underscore:@attaboy:: >> - 2013 :noexport: >> >> Any comments on the regular expression are welcome before I make >> patch. > > Thanks for working on fixing this. > > The more or less standard regexp for tags-till-end-of-line is this: > >:[[:alnum:]_@#%:]*[ \t]*$ > ^ > > With * if you want to match headlines with no tag. I may have misapplied what you suggested, but the new regexp (see below) does not work on a year headline without tags. : (defun org-datetree-find-year-create (year) :(let ((re "^\\*+[ \t]+\\([12][0-9][0-9][0-9]\\)[ \t]*\\(:[[:alnum:]_@#%:]*[ \t]*$\\)") : match) However, the suggestion helped me find the following in org-todo-line-tags-regexp \\(.*?\\([ \t]:[[:alnum:]:_@#%]+:[ \t]*\\)?$\\) Applying this regexp worked on a tag-free headline (both with and without trailing spaces) : (defun org-datetree-find-year-create (year) :(let ((re "^\\*+[ \t]+\\([12][0-9][0-9][0-9]\\)\\(.*?\\([ \t]:[[:alnum:]:_@#%]+:[ \t]*\\)?$\\)") : match) > > Please have a look at this page before submitting a patch: > http://orgmode.org/worg/org-contribute.html#sec-5 Will do. > > Thanks! -- Tim Burt www.rketburt.org "It is healthful to every sane man to utter the art within him;" -- GK Chesterton
Re: [O] org-capture, datetree, and tags
Tim Burt writes:
> Jeffrey Brent McBeth writes:
>
>> I'm trying to capture into a datetree using org-capture, but if my tree has
>> a tag on it (in particular noexport), then it creates a new datetree instead
>> of using the one I have.
>> Example .emacs:
>> (global-set-key "\C-cc" 'org-capture)
>> (setq org-capture-templates
>> '(("t" "Test" plain (file+datetree "~/Test.org")
>> "%^{Greeting} World
>> I'm going to work this time")))
>>
>> Example Test.org:
>>
>> * 2013
>> :noexport:
>> ** 2013-02 February
>> *** 2013-02-19 Tuesday
>> Hello World
>> I'm going to work this time
>>
>> So, based on the above, if I type C-cct Silly C-cc, I'll get this:
>>
>> * 2013
>> :noexport:
>> ** 2013-02 February
>> *** 2013-02-19 Tuesday
>> Hello World
>> I'm going to work this time
>> * 2013
>> ** 2013-02 February
>> *** 2013-02-19 Tuesday
>> Silly World
>> I'm going to work this time
>>
>> Thanks for your attention,
>> Jeffrey McBeth
>
> I can confirm both the behavior and a usecase for a tagged datetree.
>
> In org-datetree.el the function org-datetree-find-year-create searches for
> the year on a headline and will not match content with anything beyond the
> fourth digit.
> : (defun org-datetree-find-year-create (year)
> : (let ((re "^\\*+[ \t]+\\([12][0-9][0-9][0-9]\\)$")
> : match)
>
> In this particular case the tag in question is :noexport: with white space
> fore (and maybe aft), and the following change to the regular expression
> was tested with success.
> : (defun org-datetree-find-year-create (year)
> : (let ((re "^\\*+[ \t]+\\([12][0-9][0-9][0-9]\\)[ \t]+:noexport:[ \t]*$")
> : match)
> Of course this only matches the specific tag in this example *and* only
> matches a datetree with this tag. The regular expression needs to be
> improved to include a valid tag set as optional.
Improved the regular expression to permit multiple tags of letters,
numbers, underscores, and at signs.
: (defun org-datetree-find-year-create (year)
:(let ((re "^\\*+[ \t]+\\([12][0-9][0-9][0-9]\\)[
\t]*\\(:[[:alnum:]_@]*\\)*:*[ \t]*$")
: match)
I've tested with the following headlines:
- 2013
- both with and without trailing spaces
- 2013 :abc:
- 2013 :abc123:
- 2013 :abc123:_underscore:@attaboy::
- 2013 :noexport:
Any comments on the regular expression are welcome before I make patch.
--
Tim Burt
www.rketburt.org
"It is healthful to every sane man to utter the art within him;" -- GK
Chesterton
Re: [O] org-capture, datetree, and tags
Jeffrey Brent McBeth writes:
> I'm trying to capture into a datetree using org-capture, but if my tree has a
> tag on it (in particular noexport), then it creates a new datetree instead of
> using the one I have.
> Example .emacs:
> (global-set-key "\C-cc" 'org-capture)
> (setq org-capture-templates
> '(("t" "Test" plain (file+datetree "~/Test.org")
> "%^{Greeting} World
> I'm going to work this time")))
>
> Example Test.org:
>
> * 2013
> :noexport:
> ** 2013-02 February
> *** 2013-02-19 Tuesday
> Hello World
> I'm going to work this time
>
> So, based on the above, if I type C-cct Silly C-cc, I'll get this:
>
> * 2013
> :noexport:
> ** 2013-02 February
> *** 2013-02-19 Tuesday
> Hello World
> I'm going to work this time
> * 2013
> ** 2013-02 February
> *** 2013-02-19 Tuesday
> Silly World
> I'm going to work this time
>
> Thanks for your attention,
> Jeffrey McBeth
I can confirm both the behavior and a usecase for a tagged datetree.
In org-datetree.el the function org-datetree-find-year-create searches for
the year on a headline and will not match content with anything beyond the
fourth digit.
: (defun org-datetree-find-year-create (year)
: (let ((re "^\\*+[ \t]+\\([12][0-9][0-9][0-9]\\)$")
: match)
In this particular case the tag in question is :noexport: with white space
fore (and maybe aft), and the following change to the regular expression
was tested with success.
: (defun org-datetree-find-year-create (year)
: (let ((re "^\\*+[ \t]+\\([12][0-9][0-9][0-9]\\)[ \t]+:noexport:[ \t]*$")
: match)
Of course this only matches the specific tag in this example *and* only
matches a datetree with this tag. The regular expression needs to be
improved to include a valid tag set as optional.
--
Tim Burt
www.rketburt.org
"It is healthful to every sane man to utter the art within him;" -- GK
Chesterton
Re: [O] Using Org for a dissertation - appendices
Henri-Paul Indiogine writes: > Hi! > > 2012/5/12 Richard Lawrence : >> (Henri-Paul, do you still read this list?) > > Yes, I do. Still using orgmode each day. > > I do not have anything fancy going on and actually would like to know > how to set up appendices for LaTeX export. > > I have the following outline: > > * Review of Literature > * Methodology > * Findings > * Discussion > * Conclusion > * Footnotes > * References > * Appendices > ** Appendix A > ** Appendix B > ** Appendix C > > The LaTeX export of course does not know the that last chapter should > contain the appendices. I have tried to insert several LaTeX commands > in the orgmode file, but I could not make it work. Use the \appendix command to turn on alphabetic numbering. > > Does anyone have a suggestion? If you want the last three headlines to each have a different letter, then you make them top-level headlines instead of children: * References \appendix * Appendix A * Appendix B * Appendix C > > Thanks, > Henri-Paul -- Tim Burt www.rketburt.org "It is healthful to every sane man to utter the art within him;" -- GK Chesterton
Re: [O] Gather properties for use by babel source block?
Colin Hall writes: > Tim Burt rochester.rr.com> writes: >> >> I want to gather data from properties into something that can be used by >> a babel source block (e.g. plot the data). Searches in the manual, >> worg, and gmane have not yielded the method, but my best guess is that >> I've missed it. If so, this is simply a request for a pointer to the >> documentation I should read. > > Any luck with this, Tim? I'm trying to do something very similar. After the hints of Darlan and Suvayu last August I cobbled a workflow described below. Errors and instability in the early weeks have been resolved into the current set of workable blemishes described below the workflow. The attachment is an org file that should be a working example if gnuplot is installed and configured for org-babel. Thank you Colin for asking the question about progress, because I should have shared it with the mailing list long ago warts and all. This is an example file for gathering and plotting health data (some of which has been fudged to protect the guilty ;-). The workflow is this: 1. DAILY: Use capture templates to query for data into a datetree under the heading '2011' which has an ID property. Each data headline is marked with tags for the data class (e.g. weight, blood sugar) that is used as a hook for collection. 2. ONE-TIME: Define the plots, in this case using gnuplot (thanks to Suvayu for the noweb example), under the heading 'Calculation and Visualization'. Another one-time setup is to define propview blocks that org-collector will populate for each data class (e.g. weight). Both the ID and tags are used to extract the information. 3. ONE-TIME: Another one-time setup is to define propview blocks that org-collector will populate for each data class (e.g. weight). Both the ID and tags are used to extract the information and this is under the 'Summaries' heading. - A #+tblname is placed after the #+BEGIN to provide a hook for the babel blocks for plotting. 4. ON-DEMAND: Refresh each collector block (in this case 4 separate ones), then org-babel-execute-buffer to generate the plots. This method has been mostly working but it has a few weaknesses, borne mostly from my ignorance. I haven't thought about the problem in several months, so maybe the act of writing the questions will spur me to the act of making it better. Here are my observations and questions: - At various times in the past year the ON-DEMAND step has not worked consistently, especially in regards to the #+tblname within the collector block. Sometimes the refresh would fail, often by wiping out the existing static view and replacing with an empty line under the #+tblname. No matter what happened in the past, it is stable enough for this post. - The problem could have been one of configuration (e.g. org-collector not loaded) or data (e.g. error in the date tree) or something else entirely. I have not done sufficiently thorough troubleshooting to really identify the different problems. - Collection is done by matching the tags in the data headlines, but the same type of information can be gleaned from the properties themselves. How can a match invocation be crafted to use the properties? - This weakness comes straight from my ignorance of lisp. - Collection is done for each separate table which does not scale well as the number of tables increases. Scaling itself is not the issue with just 4 tables, but forgetting to update each table is a slight problem. - Is there a way to automate the org-collector step so that one action updates all tables? - Of course, for the current story another solution would be to create one single data table with org-collector then modify the plotting routines to extract only the necessary columns. I'd like the ability to do monolithic or separate then decide which to use for which problems. - The capture templates yield blank properties that simply clutter the drawer and make data extraction logic slightly more complicated since existence alone is not a complete test. - Can a capture template be written to ask all the questions, but not yield a property if the answer is 'null'? TCBHealth-Example.org Description: Lotus Organizer > > Cheers, > Colin. > > > > > > -- Tim Burt www.rketburt.org "It is healthful to every sane man to utter the art within him;" -- GK Chesterton
Re: [O] Wrapping of e-mail address in table when exporting to pdf through latex
Eric S Fraga writes:
> Johnny writes:
>
>> Hi,
>>
>> I have some e-mail addresses in a table that I want to export to pdf
>> thorugh latex. However, the e-mail addresses do not wrap nicely (not at
>> all) in the table, is there any way to make the latex export from org
>> enable wrapping?
>>
>> Example:
>>
>>#+ATTR_LaTeX: align=llp{2cm}
>> | ITEM| Comment| e-mail |
>> |-++--|
>> | Listed item | Some text here | this.email@shouldbe.wrapped |
>> | || |
>>
>> Thanks!
>
> As you are alluding, this is more a latex problem than an org
> one. Getting an email address to wrap is difficult. The only solution
> I can think of is to suggest a hyphenation point in each email address
> you have in the table.
>
> You can suggest hyphenation points using "\-", as in:
>
> | Listed item | Some text here | this.email@\-shouldbe.wrapped |
>
> This works, but is not pretty... but I don't think you have much in the
> way of alternative options!
>
> HTH,
> eric
The hyperref package provides a LaTeX solution, the briefest of which is
the \url{} command (and the \nolinkurl{} variant).
#+ATTR_LaTeX: align=llp{2cm}
| ITEM | Comment | e-mail
|
|--+---+-|
| ~url~ cmd| e-mail is a dead link |
\url{this.email@shouldbe.wrapped} |
| ~nolinkurl~ cmd | e-mail is just text |
\nolinkurl{this.email@shouldbe.wrapped} |
| ~mailto:~ syntax | e-mail is an mailto: link |
mailto:this.email@shouldbe.wrapped |
*** Notes for the mailto syntax
For the ~mailto:~ syntax to work the variable
~org-export-latex-href-format~ needs to use the ~url~ command instead of
~href~
(http://article.gmane.org/gmane.emacs.orgmode/44911/match=href+latex+link+url)
: (setq org-export-latex-href-format "\url{%s}")
While I prefer the ~mailto:~ syntax as more the `orgmode way', there are
two possible issues:
- config :: It requires a change to *all* LaTeX link exports
- display :: The ~mailto:~ string is also exported
I do not know what other solutions are currently possible to resolve those
issues.
--
Tim Burt
www.rketburt.org
"It is healthful to every sane man to utter the art within him;" -- GK
Chesterton
Re: [O] Specify the end of a heading even when there's still some content after it
Eric S Fraga writes:
> Emmanuel Di Pretoro writes:
>
>> Hi,
>>
>> Is there a way to ask to org-mode to add something before the
>> \end{document} of a LaTeX export?
LaTeX has the command \AtEndDocument{} which defers processing
of until \end{document} is reached. Might this suit your
need?
Tim
>
> The only thing that comes to mind would be to see if you can play with
>
> ,[ C-h v org-export-latex-final-hook RET ]
> | org-export-latex-final-hook is a variable defined in `org-latex.el'.
> | Its value is
> | ( ... )
> |
> |
> | This variable is potentially risky when used as a file local variable.
> |
> | Documentation:
> | Hook run in the finalized LaTeX buffer.
> |
> | [back]
> `
>
> and fix up the latex created to insert what you need at the right
> place?
>
> HTH,
> eric
--
Tim Burt
www.rketburt.org
"It is healthful to every sane man to utter the art within him;" -- GK
Chesterton
[O] Gather properties for use by babel source block?
I want to gather data from properties into something that can be used by a babel source block (e.g. plot the data). Searches in the manual, worg, and gmane have not yielded the method, but my best guess is that I've missed it. If so, this is simply a request for a pointer to the documentation I should read. BACKGROUND: I'm trying to complete a workflow where I capture data over time and periodically operate with it (e.g. put into a database and plot). The excellent documentation for orgmode has made certain parts easy going, but the current obstacle is extracting properties that can subsequently be operated on in babel source blocks. + [X] Capture data into properties using templates + [X] View tables of properties in org file * [X] use columnview dynamic block * [X] use org-collector + [ ] Gather properties for use by babel source block + [-] Operate on the gathered properties * [-] SQL or SQLite - [X] follow simple tutorials for proof of principle - [ ] populate database with gathered properties * [-] R - [X] follow simple tutorials - [ ] calculate statistics and populate database - [ ] plot from database - [ ] plot from table in org file Good evening, Tim
Re: [Orgmode] Re: HTML export and blogging to blogger.com
Samuel Wales writes: > Hi Nick, > > That is a great idea. > > Unfortunately, that option is simply not there for me. > > In Firefox and emacs-w3m, I only get: > > Reader Comments > (*) Allow > ( ) Don't allow > Backlinks > ( ) Allow > (*) Don't allow > > And strangely do not get what you get. I tried reducing fonts in > Firefox also; the same thing showed up. > > I wonder if we are using different versions of Blogger? This might be true. At the bottom of the Settings | Basic tab is the entry "Select post editor". The "Updated editor" has features that might be apropos to these line break problems. http://www.google.com/support/blogger/bin/answer.py?answer=156829 > > Then I went to Settings -> Formatting and found this: > > - > > Convert line breaks > > If Yes is selected, single hard-returns entered in the Post Editor > will be replaced with single tags in your blog, and two > hard-returns will be replaced with two tags (). > > - > > But I set it to No and there was no difference; the paragraphs did not > get filled. > > So I guess we are back to my 3 questions: unfill hook, HTML unfill, or > better unfill-region. > > > Samuel > > ___ > Emacs-orgmode mailing list > Please use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] org-googlecl : enhancements - replace existing blog entries.
Richard Riley writes: > The org-googlecl package has been extended a little. > > http://splash-of-open-sauce.blogspot.com/2010/09/now-org-googlecl-supports-deleting-of_14.html > > It now detects if you try to blog an entry with the same title as an > existing one and prompts you to view and/or remove one or more entries > with the same name. Obviously very useful for just updating an entry (NB > the url will change unfortunately). There is also a footer option and > default labels (tags) if none are specified on the org entry you are > blogging. Tags as labels for the blog is a welcome feature. > It's working pretty cleanly now but any feedback appreciated - > its a pretty handy complement to org-mode if you maintain a > blogger/blogspot account. That's an understatement. Publishing from org to blogger is nearly transparent and takes only seconds to confirm the information (e.g. title, labels). It is a treat to use org-googlecl. Thank you Richard. Tim > The elisp snippets you will see above were all > blogged from my dotemacs files which are all in org files using this > function. > > regards > > r. > > > ___ > Emacs-orgmode mailing list > Please use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Blogging org entries using google command line.
Richard Riley writes: > Tim Burt writes: > >> Could Richard Riley have solved my problem? Yes he did. >> http://naturallogofx.rketburt.org/2010/09/could-richard-riley-have-solved-my.html > > Glad its of some use. It (googlecl) has been on my "must check it out" > list for a while ;) > > Its just at test stage but taking shape - I'm having to relearn elisp > again ... I'll "git" (!) it in the next few days. But here's the latest code > posted using itself and cleaned up a bit. Note the two defvars to > set. You can prefix (C-u) the call to get prompted for the blog name. > > http://splash-of-open-sauce.blogspot.com/2010/09/improved-code-for-googlecl-blog_08.html Nice improvements. Will use. > As a side note, I intend to create a module org-googlecl (org google > command line) with corresponding namespace for customisations. I'm sure > then that people more familiar with the publishing portion of org can > supe it up a bit more. I look forward to that. Again, many thanks. > > cheers > > r. > >> >> Thank you, thank you, thank you, >> Tim >> >> Richard Riley writes: >> >>> Using the google command line you can get some super access to all your >>> Google resources - including docs, calendars & blogs. >>> >>> http://code.google.com/p/googlecl/ >>> >>> Once you have installed it and set up your OAUTH you can easily >>> manipulate/add/delete things in your google hosted data. >>> >>> While not polished and featuring hard coded blog name the following >>> function uses the google command line tool to blog the current >>> org-entry. >>> >>> (defun rgr/org-blog-entry () >>> (interactive) >>> (save-excursion >>> (let ((tmpheading (org-get-heading))) >>> (goto-char (org-entry-beginning-position)) >>> (set-mark (org-entry-end-position)) >>> (let*((tmpfile (make-temp-file "org-blog-html-")) >>>(blog-command (concat "google blogger post --blog \"Open >>> Sauce\" --title '" tmpheading "' " tmpfile ))) >>> (org-export-as-html 1 nil nil (find-file-noselect tmpfile) t) >>> (with-current-buffer (get-file-buffer tmpfile) (save-buffer)) >>> (start-process-shell-command "Google Blog" "*googlecl*" >>> blog-command) >>> >>> At some point I'll try and make it more generic with customised options >>> if no one beats me to it .. >>> >>> regards >>> >>> r. >> >> ___ >> Emacs-orgmode mailing list >> Please use `Reply All' to send replies to the list. >> Emacs-orgmode@gnu.org >> http://lists.gnu.org/mailman/listinfo/emacs-orgmode >> ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Blogging org entries using google command line.
Could Richard Riley have solved my problem? Yes he did. http://naturallogofx.rketburt.org/2010/09/could-richard-riley-have-solved-my.html Thank you, thank you, thank you, Tim Richard Riley writes: > Using the google command line you can get some super access to all your > Google resources - including docs, calendars & blogs. > > http://code.google.com/p/googlecl/ > > Once you have installed it and set up your OAUTH you can easily > manipulate/add/delete things in your google hosted data. > > While not polished and featuring hard coded blog name the following > function uses the google command line tool to blog the current > org-entry. > > (defun rgr/org-blog-entry () > (interactive) > (save-excursion > (let ((tmpheading (org-get-heading))) > (goto-char (org-entry-beginning-position)) > (set-mark (org-entry-end-position)) > (let*((tmpfile (make-temp-file "org-blog-html-")) >(blog-command (concat "google blogger post --blog \"Open > Sauce\" --title '" tmpheading "' " tmpfile ))) > (org-export-as-html 1 nil nil (find-file-noselect tmpfile) t) > (with-current-buffer (get-file-buffer tmpfile) (save-buffer)) > (start-process-shell-command "Google Blog" "*googlecl*" > blog-command) > > At some point I'll try and make it more generic with customised options > if no one beats me to it .. > > regards > > r. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Eliminate line breaks in html
John Hendy writes: > I use org for exporting to html and then pasting into blogger I use this process also for Blogger > ... but every time I do I need to delete line breaks. ... but I do not need to delete line breaks. See http://naturallogofx.rketburt.org/2010/07/linebreaks-blogger-and-org-mode.html for an article that describes what I do. The fix for me was in the Blogger settings, not anything in emacs. > Is there a way to get org to just publish the blob without breaking > lines every time? I do not know how to prevent line breaks in the export, but nor have I needed to do that. > I'm guessing it has to do with my minor fill mode as the line breaks > tend to be the same as they are in org. > > In typical export, everything is surrounded by tags but in blogger on > doesn't have these and thus line breaks are line breaks. The article reference above indicates how to stop Blogger from presenting an input linebreak (e.g. newline character) as an output linebreak. > I could resort to explicit html every time I post (requiring > for every line break) but this would also require fixing all > pre-existing posts which is pretty much not an option. > > Any idea what I could do? Let me know if the article reference does not help solve the issue. Tim > > > Thanks, > John > ___ > Emacs-orgmode mailing list > Please use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] latex-export + columnview: misinterpretation of section prefixes as emphasis
Carsten Dominik writes:
> Hi Juan,
> On May 31, 2010, at 5:38 AM, Juan Pechiar wrote:
>
>> Hi!
>>
>> The test file below contains a columnview table showing section
>> headers.
>>
>> Export to HTML works OK: the asterisks inside the table are
>> transformed into indentation.
>>
>> Export to LaTeX: asterisk pairs are interpreted as emphasis, resulting
>> in an incorrect renering of asterisks and bold asterisks.
>>
>> Following the code, I got lost at org-export-latex-fontify.
>>
>> I will keep searching for what is happening, but any guidance will be
>> appreciated.
>
> I have fixed at least part of the problem, so the stars will no longer
> be
> interpreted as emphasis.
>
> However, I am still getting strange results. FOrmatting a latex file
> with this:
>
> \begin{center}
> \begin{tabular}{l}
> ITEM \\
> \hline
> * There comes the table \\
> * first \\
> ** second\\
> *** third\\
> *** other third \\
> fourth \\
> ** other second \\
> \end{tabular}
> \end{center}
>
> somehow swallows some of the stars, but seemingly random.
> For example, the star before "There" remains, but the star
> before "first" disappears.
>
> This must be some strange LaTeX thing - does anyone
> understand what is going on here?
This is indeed a LaTeX thing. The newline sequence (\\) has more than
one signature
- \\ :: simple newline
- \\[additionalSpace] :: newline with additionalSpace
- \\*[additionalSpace] :: same as above but will not break a page
After the \\ sequence, LaTeX looks for a [ or a * in case the optional
argument exists. In the example above the star is found as _part of a
command sequence_ and is therefore not available as something to
typeset.
One solution in this situation is to put an empty group before the
stars:
\begin{center}
\begin{tabular}{l}
ITEM \\
\hline
{}* There comes the table \\
{}* first \\
{}** second\\
{}*** third\\
{}*** other third \\
{} fourth \\
{}** other second \\
\end{tabular}
\end{center}
I will think on other possible options. I hope this helps.
Tim
>
> - Carsten
>
>
>>
>> Thanks!
>>
>> .j.
>>
>>
>> Test file:
>>
>> #+COLUMNS: %25ITEM
>>
>> * There comes the table
>>
>> #+BEGIN: columnview :vlines 1 :id global
>> | | ITEM|
>> |---+-|
>> | | * There comes the table |
>> | | * first |
>> | | ** second |
>> | | *** third |
>> | | *** other third |
>> | | fourth |
>> | | ** other second |
>> | / | <> |
>> #+END:
>>
>> * first
>> ** second
>> *** third
>> *** other third
>> fourth
>> ** other second
>>
>>
>> LaTeX output:
>>
>> \begin{tabular}{l}
>> ITEM \\
>> \hline
>> * There comes the table \\
>> * first \\
>> ** second\\
>> *** third\\
>> \textbf{*} other third \\
>> \textbf{**} fourth \\
>> ** other second \\
>> \end{tabular}
>>
>>
>> And the PDF display reads:
>>
>> ITEM
>> * There comes the table
>> first
>> * second
>> ** third
>> * other third
>> ** fourth
>> * other second
>>
>>
>>
>>
>> ___
>> Emacs-orgmode mailing list
>> Please use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
> - Carsten
>
>
>
>
> ___
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Fail to compile a file's LaTeX export
David Maus writes:
> Leo wrote:
> >On 2010-03-20 20:29 +, Leo wrote:
> >> Hello,
> >>
> >> While taking some common lisp notes, I found compiling the following org
> >> file's LaTeX output fails.
> >>
> >>
> >> #+title: test file
> >>
> >> * one
> >> 1. (char "string" 2) => #\r
> >> 2. define-modify-macro
> >> 3. (code-char 66) => #\B and (char-code #\B) => 66
> >> 4. terpri and fresh-line
> >> 5. "~n&" print a new line if not at the beginning of a line and then
> >> n-1 new lines.
> >>
> >>
> >> Leo
>
> >BTW, this was tested with the devel version of org.
>
> Can confirm this for
>
> Org-mode version 6.34trans (release_6.34c.225.g1576)
>
> on
>
> GNU Emacs 24.0.50.1 (i486-pc-linux-gnu, GTK+ Version 2.18.7) of
> 2010-03-11 on elegiac, modified by Debian
>
> Exporting to LaTeX works fine but compiling the LaTeX file errors out
> with:
>
> ,
> | ERROR: LaTeX Error: Something's wrong--perhaps a missing \item.
> |
> | --- TeX said ---
> |
> | See the LaTeX manual or LaTeX Companion for explanation.
> | Type H for immediate help.
> | ...
> |
> | l.37 \item
> |define-modify-macro
> | --- HELP ---
> | The most probable cause is an omitted \item command in a list-making
> | environment. It is also caused by forgetting the argument of a
> | thebibliography environment.
> `
>
> Where the LaTeX code for the enumerate environment reads:
>
> ,
> | \begin{enumerate}
> | \item (char ``string'' 2) => \#\r
> | \item define-modify-macro
> | \item (code-char 66) => \#\B and (char-code \#\B) => 66
> | \item terpri and fresh-line
> | \item ``\~{}n\&'' print a new line if not at the beginning of a line and
> then n-1 new lines.
> | \end{enumerate}
> `
>
> I suppose the \#\r is the problematic piece, will look into it
> tomorow.
Indeed \r is one of the problematic pieces; the other is the \B. The
LaTeX exporter does not modify them since they look like LaTeX
commands already, which is true in the case of \r (see below) but not
in that for \B. Either way I don't get the impression that either is
intended to be used as a LaTeX command so they should be marked
somehow for conversion, but I don't know what would be most
satisfactory.
The \r is a LaTeX command that puts a ring accent over the next
character. For example, \r{A} looks somewhat like the Angstrom unit.
My fractured fairy tale is that the generated LaTeX code breaks
because the character following \r is not one that can be accented in
a way that keeps the lists (especially the \item command) sane.
Tim
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: [org-beamer] \alert
Eric S Fraga writes:
> At Thu, 28 Jan 2010 18:58:38 +0100,
> Carsten Dominik wrote:
>
> [...]
>
> >
> > Is there a LaTeX command that can figure out if it is running a beamer
> > class?
> > If yes, a possible solution would be to redefine \alert in LaTeX when
> > not doing BEAMER.
> >
> > - Carsten
> >
>
> This must be possible but my latex (and tex) programming capabilities
> are even worse than my elisp... :(
>
> For any LaTeX expert out there, is there an easy way to determine
> whether a particular macro has been defined? If so, we wouldn't even
> need to check for beamer, simply for \alert.
Use the
\ifx\undefined ... \else ... \fi
construct to determine if a command already exists, and then to take
action in the appropriate case. Test the example below both as-is and
with the first ~\newcommand*{\thisalert}~ commented out to see the
different results.
: \documentclass{article}
: \newcommand*{\thisalert}{Do this.}
: % Test for existence of \thisalert.
: % Create or modify the command accordingly.
: \ifx\thisalert\undefined%
: \newcommand*{\thisalert}{Do that.}%
: \else%
: \renewcommand*{\thisalert}{Do this differently.}
: \fi
: \begin{document}
:
: \thisalert
:
: \end{document}
I hope this is of use,
Tim
>
>
> ___
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Do we still have XEmacs users?
Yes. Carsten Dominik writes: > Do we still have XEmacs users around here? > > - Carsten > > > ___ > Emacs-orgmode mailing list > Remember: use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] fullpage.sty replacement [WAS: Problem with LaTeX snippets preview]
Carsten ---
Ah, I see. I had not become one with the thread to see that this was
not used for documents. Now I get to learn something new. It's a
good day.
Good evening,
Tim
Carsten Dominik writes:
> Hi Tim,
>
> I have applied your patch, thanks.
>
> The header for the LaTeX files used to produce PDF export independent
> from this. The stuff here is only used to create small images that
> will be displayed in Emacs or used in HTML export.
>
> - Carsten
>
> On Sep 26, 2009, at 12:36 PM, Tim Burt wrote:
>
> >
> > In another thread there was a discussion about replacing the
> > use of fullpage.sty with its functionality.
> > NickD> Looks like the culprit is fullpage.sty - seems to be required
> > NickD> by the LaTeX code that org-preview-latex-fragment generates.
> >
> > CarstenD> I believe the reason that this is used it to make sure that
> > CarstenD> wide formulas can still be formatted reasonably well,
> > CarstenD> without additional line breaks. I guess we could inline
> > CarstenD> the content of this small package.
> > CarstenD>
> > CarstenD> Would somebody like to try to replace this with just the
> > CarstenD> margin setting commands of fullpage.sty?
> > With continued thanks to Patrick Daly, the author of fullpage.sty and
> > my favorite LaTeX book "A Guide to LaTeX2e", I put the margin and text
> > size settings accomplished by fullpage.sty in org-format-latex-header
> > of org.el.
> > Org-mode version 6.30trans (release_6.30d.882.gdbd63.dirty)
> > The diff below is offered as a step towards inlining the
> > functionality.
> >
> > The caveats:
> > 1. This is untested
> > - When I execute org-export-as-pdf some other header appears in
> > the .tex file, and I have not yet discovered the source of this
> > other header.
> > 2. This is the first time I've done a git diff.
> >
> > If there are troubles in testing I will be happy to help resolve.
> >
> > Good morning,
> > Tim
> >
> > Output of git diff org.el:
> > diff --git a/lisp/org.el b/lisp/org.el
> > index 89d3bc8..8772968 100644
> > --- a/lisp/org.el
> > +++ b/lisp/org.el
> > @@ -2678,13 +2678,24 @@ This is a property list with the following
> > properties:
> > :type 'plist)
> >
> > (defcustom org-format-latex-header "\\documentclass{article}
> > -\\usepackage{fullpage} % do not remove
> > \\usepackage{amssymb}
> > \\usepackage[usenames]{color}
> > \\usepackage{amsmath}
> > \\usepackage{latexsym}
> > \\usepackage[mathscr]{eucal}
> > -\\pagestyle{empty} % do not remove"
> > +\\pagestyle{empty} % do not remove
> > +\\setlength{\\textwidth}{\\paperwidth}
> > +\\addtolength{\\textwidth}{-3cm}
> > +\\setlength{\\oddsidemargin}{1.5cm}
> > +\\addtolength{\\oddsidemargin}{-2.54cm}
> > +\\setlength{\\evensidemargin}{\\oddsidemargin}
> > +\\setlength{\\textheight}{\\paperheight}
> > +\\addtolength{\\textheight}{-\\headheight}
> > +\\addtolength{\\textheight}{-\\headsep}
> > +\\addtolength{\\textheight}{-\\footskip}
> > +\\addtolength{\\textheight}{-3cm}
> > +\\setlength{\\topmargin}{1.5cm}
> > +\\addtolength{\\topmargin}{-2.54cm}"
> > "The document header used for processing LaTeX fragments."
> > :group 'org-latex
> > :type 'string)
> >
> >
> > ___
> > Emacs-orgmode mailing list
> > Remember: use `Reply All' to send replies to the list.
> > Emacs-orgmode@gnu.org
> > http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] fullpage.sty replacement [WAS: Problem with LaTeX snippets preview]
In another thread there was a discussion about replacing the
use of fullpage.sty with its functionality.
NickD> Looks like the culprit is fullpage.sty - seems to be required
NickD> by the LaTeX code that org-preview-latex-fragment generates.
CarstenD> I believe the reason that this is used it to make sure that
CarstenD> wide formulas can still be formatted reasonably well,
CarstenD> without additional line breaks. I guess we could inline
CarstenD> the content of this small package.
CarstenD>
CarstenD> Would somebody like to try to replace this with just the
CarstenD> margin setting commands of fullpage.sty?
With continued thanks to Patrick Daly, the author of fullpage.sty and
my favorite LaTeX book "A Guide to LaTeX2e", I put the margin and text
size settings accomplished by fullpage.sty in org-format-latex-header
of org.el.
Org-mode version 6.30trans (release_6.30d.882.gdbd63.dirty)
The diff below is offered as a step towards inlining the
functionality.
The caveats:
1. This is untested
- When I execute org-export-as-pdf some other header appears in
the .tex file, and I have not yet discovered the source of this
other header.
2. This is the first time I've done a git diff.
If there are troubles in testing I will be happy to help resolve.
Good morning,
Tim
Output of git diff org.el:
diff --git a/lisp/org.el b/lisp/org.el
index 89d3bc8..8772968 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -2678,13 +2678,24 @@ This is a property list with the following properties:
:type 'plist)
(defcustom org-format-latex-header "\\documentclass{article}
-\\usepackage{fullpage} % do not remove
\\usepackage{amssymb}
\\usepackage[usenames]{color}
\\usepackage{amsmath}
\\usepackage{latexsym}
\\usepackage[mathscr]{eucal}
-\\pagestyle{empty} % do not remove"
+\\pagestyle{empty} % do not remove
+\\setlength{\\textwidth}{\\paperwidth}
+\\addtolength{\\textwidth}{-3cm}
+\\setlength{\\oddsidemargin}{1.5cm}
+\\addtolength{\\oddsidemargin}{-2.54cm}
+\\setlength{\\evensidemargin}{\\oddsidemargin}
+\\setlength{\\textheight}{\\paperheight}
+\\addtolength{\\textheight}{-\\headheight}
+\\addtolength{\\textheight}{-\\headsep}
+\\addtolength{\\textheight}{-\\footskip}
+\\addtolength{\\textheight}{-3cm}
+\\setlength{\\topmargin}{1.5cm}
+\\addtolength{\\topmargin}{-2.54cm}"
"The document header used for processing LaTeX fragments."
:group 'org-latex
:type 'string)
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Export bug: LaTeX TOC headline numbers above 100 overlap headline
Carsten Dominik writes:
> On Sep 25, 2009, at 2:10 AM, Jeff Kowalczyk wrote:
>
> > When the headline count for a pdftolatex export gets to be more than
> > 100 lines, the TOC renders with the headline number directly
> > touching the headline text. More than 1,000, and it starts to overlap.
>
> This is a LaTeX issue, which I do not know how to fix.
>
> - Carsten
>
> >
> > It would seem that LaTeX calculates the space to allocate for the
> > headline number based on too few initial entries.
> >
> > I have included a simple test case below.
* Executive Summary
Add the following two lines to the org file (after ensuring you have
the tocloft.sty package installed and visible to LaTeX).
#+LaTeX_HEADER: \usepackage{tocloft}
#+LaTeX_HEADER: \setlength{\cftsecnumwidth}{3em}
* Supporting Jabber
The formatting for Table of Contents (and its kin) is set deep in the
class definitions. The tocloft package provides user-level commands
to modify those internals which the tocloft documentation describes
quite well, including a figure that shows a value called 'numwidth' is
the length of the box in which the number is set. This value can be
different for each sectioning level (e.g. chapter, section,
subsection). In the test case below, the first org level[1] is being
exported as a \section{}. The box length for section can be set by
the value of \cftsecnumwidth using the \setlength command, as in
\setlength{\cftsecnumwidth}{3em}
The second argument must have a unit of length which in this example
is 'em' (the width of a capital M). This allows the width of the box
to scale with font changes, but other units are certainly permissible
(e.g. cm, mm, in).
Good morning,
Tim
[1] Note: This test case was run using the default org export
variables for LaTeX which means the article class was used. If
another class is used (e.g. report) then the first org level should be
exported as a \chapter{}. In this case, replace \cftsecnumwidth with
\cftchapnumwidth.
> >
> > Thanks,
> > Jeff
> >
> > * Headline 0
> > * Headline 1
> > * Headline 2
> > * Headline 3
> > * Headline 4
> > * Headline 5
> > * Headline 6
> > * Headline 7
> > * Headline 8
> > * Headline 9
> > * Headline 10
> > * Headline 11
> > * Headline 12
> > * Headline 13
> > * Headline 14
> > * Headline 15
> > * Headline 16
> > * Headline 17
> > * Headline 18
> > * Headline 19
> > * Headline 20
> > * Headline 21
> > * Headline 22
> > * Headline 23
> > * Headline 24
> > * Headline 25
> > * Headline 26
> > * Headline 27
> > * Headline 28
> > * Headline 29
> > * Headline 30
> > * Headline 31
> > * Headline 32
> > * Headline 33
> > * Headline 34
> > * Headline 35
> > * Headline 36
> > * Headline 37
> > * Headline 38
> > * Headline 39
> > * Headline 40
> > * Headline 41
> > * Headline 42
> > * Headline 43
> > * Headline 44
> > * Headline 45
> > * Headline 46
> > * Headline 47
> > * Headline 48
> > * Headline 49
> > * Headline 50
> > * Headline 51
> > * Headline 52
> > * Headline 53
> > * Headline 54
> > * Headline 55
> > * Headline 56
> > * Headline 57
> > * Headline 58
> > * Headline 59
> > * Headline 60
> > * Headline 61
> > * Headline 62
> > * Headline 63
> > * Headline 64
> > * Headline 65
> > * Headline 66
> > * Headline 67
> > * Headline 68
> > * Headline 69
> > * Headline 70
> > * Headline 71
> > * Headline 72
> > * Headline 73
> > * Headline 74
> > * Headline 75
> > * Headline 76
> > * Headline 77
> > * Headline 78
> > * Headline 79
> > * Headline 80
> > * Headline 81
> > * Headline 82
> > * Headline 83
> > * Headline 84
> > * Headline 85
> > * Headline 86
> > * Headline 87
> > * Headline 88
> > * Headline 89
> > * Headline 90
> > * Headline 91
> > * Headline 92
> > * Headline 93
> > * Headline 94
> > * Headline 95
> > * Headline 96
> > * Headline 97
> > * Headline 98
> > * Headline 99
> > * Headline 100
> > * Headline 101
> > * Headline 102
> > * Headline 103
> > * Headline 104
> > * Headline 105
> > * Headline 106
> > * Headline 107
> > * Headline 108
> > * Headline 109
> > * Headline 110
> > * Headline 111
> > * Headline 112
> > * Headline 113
> > * Headline 114
> > * Headline 115
> > * Headline 116
> > * Headline 117
> > * Headline 118
> > * Headline 119
> > * Headline 120
> >
> >
> >
> >
> >
> >
> >
> >
> > ___
> > Emacs-orgmode mailing list
> > Remember: use `Reply All' to send replies to the list.
> > Emacs-orgmode@gnu.org
> > http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
>
>
> ___
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmod
Re: [Orgmode] Re: How to get \\ in title or author?
Nick Dokos writes:
> Bastien wrote:
>
> > Sébastien Vauban writes:
> >
> > >> Maybe \linebreak is less context-sensitive than \newline, which would
> > >> mean
> > >> that there are more contexts (like \title and \author) in which it
> > >> behaves
> > >> as expected. Just a guess.
> > >
> > > I've asked the question on FCTT (fr.comp.text.tex) and already got an
> > > answer
> > > of Maneul Pegourie-Gonnard (who is expert on that matter):
> > >
> > > http://groups.google.fr/group/fr.comp.text.tex/browse_thread/thread/1b1af2e5291270e2#
> > >
> > > Sorry (for the others), it's in French.
> >
> > Merci! Here is a summary:
> >
> > - none of \\ \linebreak or \newline change a paragraph, they just start
> > a new line
> >
> > - with \linebreak, LaTeX tries to justify the resulting text, not with
> > \newline
> >
> > - \linebreak can take an argument to let LaTeX decides whether the line
> > should be broken or not. The default \linebreak always triggers a
> > break, but \linebreak[2] will let LaTeX decides depending on whether
> > the result is acceptable or not, and \linebreak[0] prevents any line
> > break...
> >
> > - \\ can take two arguments: one star and one digit. The star prevents
> > the line break to trigger a page break, and the digit lets you add a
> > vertical space between the two lines.
> >
> > In environments like \flushleft \flushright \centering \raggedleft
> > \raggedright, \\ doesn't have its normal definition (whereas \newline
> > behaves normally).
> >
> > - \newline is the version of \\ with no argument
> >
>
> Bastien,
>
> Thanks for the summary. There is still one problem, I think, with #+AUTHOR:
>
> \author{one \\ two}
>
> and
>
> \author{one \linebreak two}
>
> behave differently (the \linebreak has no effect), so if one wants the
> first behavior, the exporter's penchant to change \\ to
> \\textbackslash{} will not allow it. I'm not sure why \title and \author
> behave differently: I guess it's because \author is expanded inside a
> \tabular, whereas \title is not.
Indeed, multiple authors should be separated by two backslashes (\\)
in the \author{} command[*] in the standard LaTeX classes
(e.g. article, report, book). Nick has correctly noted that the
argument of \author{} is used inside a tabular environment, and \\ has
a special meaning that should be added to Bastien's summary above.
- In a tabular environment the \\ is necessary to signal the
end of one row and the beginning of the next.
So, from the perspective of standard LaTeX classes, any instance of \\
in the \author{} command should not be converted during export.
Good afternoon,
Tim
[*] Bastien has also reported that \\ works in a recent message to the
mailing list. If that was an experimental result, then this reply
only adds theoretical support so that others don't have to get out
their LaTeX debugging skills and "dust them off" (as Nick said ;-).
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Possible buglet in latex export
Robert Goldman writes:
> When I do a latex export, a simple URL in text, or a simple link url of
> the form [[URL]] --- with no description --- gets emitted as
>
> \href{URL}{URL}
>
> which causes Latex to crash for me.
The first guess is that the string 'URL' in the post is not the actual
string that "causes Latex to crash". The next guess is that 'URL' is
actually a string with one of LaTeX's 10 special characters, with a
popular one being underscore (_) in this context.
>
> I believe that this is because it won't accept a URL as the second
> argument to href.
The second argument to \href is simply a string that LaTeX can render,
so a URL is fine.
>
> Changing the \href command to \url fixes the latex problem.
>
> So I wonder if we need to catch this special case of a description-less
> URL and treat it specially in latex export for the benefit of latex's
> hyperref package.
>
> I'm not an expert on hyperref, by any means, nor do I know the innards
> of latex export, so I could be missing something here. However the
> description of \url in the hyperref manual says the following:
>
> \url{URL}
>
> Similar to \href{URL}{\nolinkurl{URL}}
>
> ...which suggests to me that using the URL without some kind of magical
> protection (provided by \nolinkurl) may lead to bad things.
A URL can be used, but any special characters must be protected
somehow. The \nolinkurl in the second argument provides such
protection, as does the \url solution mentioned above.
>
> best,
> r
>
>
> ___
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Tim Burt
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Subfloats in LaTeX
Raffi ---
The answer addresses the question behind "I've never tried to do this in
LaTeX", where 'this' is a group of figures.
> Dear community,
>
> How do I stick a group of figures together (i.e. so that I have Fig. 1
> and then a, b, c)?
The short answer is to use the ~\subfloat~ command from the =subfig=
package. The package can be found on CTAN at
http://tug.ctan.org/tex-archive/macros/latex/contrib/subfig/.
The following LaTeX document source demonstrates the technique,
including how to identify and reference subfigures.
#+begin_src latex
\documentclass{article}
\usepackage{graphicx}
\usepackage{subfig}
\begin{document}
\begin{figure}
\centering
\subfloat[Red eye, up horn.]{\includegraphics[width=0.33\textwidth]{nrocinu}}
\hfill
\subfloat[More
right-looking]{\includegraphics[width=0.33\textwidth]{nrocinu2}}
\\
\subfloat[Geometric,
right-looking]{\includegraphics[width=0.33\textwidth]{nrocinu3}}
\hfill
\subfloat[[Geometric, left-looking (and a bit
jagged)]{\includegraphics[width=0.33\textwidth]{nrocinu4}}
\\
\mbox{}\hfill
\subfloat[More depth of
character\label{fig:curr}]{\includegraphics[width=0.33\textwidth]{org-mode-unicorn}}
\hfill\mbox{}
\caption{The changing styles of the org-mode unicorn.}
\label{fig:all}
\end{figure}
%
The unicorns in Figure~\ref{fig:all} are the JPEG versions found on
\texttt{http://orgmode.org/img}.
Figure~\ref{fig:all}\subref{fig:curr} is the current form on
\texttt{http://orgmode.org}.
\end{document}
#+end_src
>
> Alternatively, is there a way I can keep images inline and yet use
> captions? Whenever I add a #+CAPTION:, it's turned into \figure and
> floating is turned on.
>
> What I'm trying to do is make a section that consists of a sequence of images.
>
> I've searched the orgmode manual but can't figure out a way short of
> generating the LaTeX file and editing it directly (hardly ideal!).
>
> That said, I've never tried to do this in LaTeX so I guess it may not
> be possible (although it would surprise me!).
>
>
> Thank you very much,
>
> - Raffi.
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] unicorn
Christopher Suckling writes: > > On 27 Feb 2009, at 18:47, Russell Adams wrote: > > > In the spirit of Org, we need a folding unicorn! ;] > > http://www.pajarita.org/aep/pajaritas/pajarita3-4.pdf In the spirit of Org I made a fold*ed* unicorn. http://www.flickr.com/photos/tcburt/sets/72157614543357071/ The model is from "Mythological Creatures and the Chinese Zodiac in Origami" by John Montroll. The designers and developers of origami models amaze me with their ingenuity and ability, which is a strikingly similar sentiment I have for the org community. Tim ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Counting of TODOs
Flávio de Souza writes: > Thanks a lot! Sorry for this basic question... It was my pleasure. And since this is my first time responding on this mailing list, I hope the answer was both correct and helpful. If so, then it is just a glimmer of the help available in this group. All the best, Tim ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Counting of TODOs
Flávio de Souza writes: > When I view the Global TODO list, altough all items are in the list. > > The summary shows the header counting wrongly. > > I think I messed up the configuration, but I do not know how to fix. > > See the picture that explains better the problem: > > http://picasaweb.google.com/flaviostz/Pessoal/photo?authkey=9o-gs3mU-rs#5237276931027050658 > The "count" is not a count, but a numeric prefix to regenerate the agenda buffer with only the corresponding TODO keyword displayed. For example, your screenshot shows Available with `N r': (0)ALL (1)TODO (2)WAITING (3)DONE which filtering to see only WAITING entries is as simple as typing 2 r This behavior is indicated in the org manual in the discussion of C-c a T Like the above, but allows selection of a specific TODO keyword. You can also do this by specifying a prefix argument to C-c a t. With a C-u prefix you are prompted for a keyword, and you may also specify several keywords by separating them with â|â as boolean OR operator. With a numeric prefix, the Nth keyword in org-todo-keywords is selected. The r key in the agenda buffer regenerates it, and you can give a prefix argument to this command to change the selected TODO keyword, for example 3 r. If you often need a search for a specific keyword, define a custom command for it (see Section 10.2 [Agenda dispatcher], page 67). Matching specific TODO keywords can also be done as part of a tags search (see Section 6.3 [Tag searches], page 43). Good morning, Tim ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
