[O] Installing from git
Hello. I'm quite confused with the installation options. Recently started out a Debian base system and compiled Emacs from the bzr repository. That came out fine, so I ran 'make install' and now Emacs 24.4.50 sits in /usr/local/bin, /usr/local/share, etc. I want to install the master branch of org-mode. Currently I followed these steps: - cd ~/org_from_git/ - git clone git://orgmode.org/org-mode.git ¿Do i need to tweak 'local.mk' so the prefix variable points to /usr/local/share before running make? ¿Which make option should i use (besides 'make autoloads')? Thanks in advance.
Re: [O] Installing from git
It seems i'm flooding John's inbox trying to send back this message into the discussion. I'm deeply sorry for that. I did what John suggested: - git clone... - cd to the repository - make (which i think does two things, byte-compilation and generating org-loaddefs.el) - add lisp dir to load-path It did worked since M-x org-version shows the right path (and version), but i'm used to browse the Info manual quite regularly. Before switching to GNU/Linux I used to install the ELPA package on a freshly unpacked Emacs (trunk builds for Windows); it was a pretty straightforward process and it seems to take care of everything. I'm not going to do that again since the ELPA package comes from the maint branch. Achim Gratz writes: > The default install method installs into site-lisp, not into the Emacs > install directory. The reason I keep advocating that method is that > conveniently the buil-in load-path is already set up to do the right > thing from the very beginning (you only need to remember to require > org-loaddefs from your .emacs) and you can fall back easily to the > built-in Org from Emacs itself if needed. Thanks for your reply. Which one is the default install method? If it's 'make install', do i need to tweak local.mk because of the location of my Emacs installation (as explained here: http://orgmode.org/worg/dev/org-build-system.html#sec-4-1-3)? In my system (Debian) Emacs is in /usr/local/. And does this method allows to have the latest info manual without overriding the built-in org-mode installation? 2014-06-30 18:51 GMT-04:00 John Hendy : > On Mon, Jun 30, 2014 at 5:44 PM, Vicente Vera > wrote: > > Hello. I'm quite confused with the installation options. > > > > Recently started out a Debian base system and compiled Emacs from the bzr > > repository. That came out fine, so I ran 'make install' and now Emacs > > 24.4.50 sits in /usr/local/bin, /usr/local/share, etc. > > > > I want to install the master branch of org-mode. Currently I followed > these > > steps: > > > > - cd ~/org_from_git/ > > - git clone git://orgmode.org/org-mode.git > > > > ¿Do i need to tweak 'local.mk' so the prefix variable points to > > /usr/local/share before running make? > > ¿Which make option should i use (besides 'make autoloads')? > > Did you search around a bit? There's lots of posts with people's > setups. You certainly *can* install over the top of the Org that came > with your version of Emacs (pointing it to install to > /usr/local/share, I suppose), though I've never gone that route. Some > mailing list examples from googling about Orgmode git installation: > - Achim's post: > http://lists.gnu.org/archive/html/emacs-orgmode/2013-05/msg00609.html > - My setup: > http://lists.gnu.org/archive/html/emacs-orgmode/2014-04/msg00396.html > > From mine, you'll note I never "install" Org -- just clone to a > directory, make, and tell Emacs about it in .emacs... done! > > > John > > > > > Thanks in advance. >
Re: [O] Installing from git
Thank you for your replies, I think i'm beginning to understand the process. These are the changes I made to local.mk: prefix = /usr/local/share datadir = /usr/local/share/emacs/24.4.50/etc/org (actually, this directory belongs to the built-in Org installation) Then: $ make $ sudo make install And it worked fine. The info manual is now updated, so is everything else. So, overall, the purpose of running 'make install' (or 'make up2', to also pull from the Git repository) is to avoid overriding the default Org installation that comes with Emacs? Going through the variables in local.mk it seems this is the idea, except maybe for 'infodir' which in my case points to the place where Emacs threw all its info files (including Org). To sum up, the process made the following changes on my system: - Org lisp files from Git now reside in /usr/local/share/emacs/site-lisp (which is in load-path by default). The original built-in Org lisp files are untouched. - M-x org-version shows the correct updated version and location. - M-x info shows the updated info manual which now resides in /usr/local/share/info (I think it replaced the built-in manual?). - Org data files now reside in /usr/local/share/emacs/24.4.50/etc/org (replacing the built-in files?). No extra elisp code was needed (adding the cloned repository to load-path, etc.).
[O] Cannot build documentation (release_8.3beta-155-g82b64d)
Hello, recently I tried to install the latest development snapshot from Git through the following procedure, which has worked for me perfectly until now: - make cleanall - make up0 - make install When the build system gets to creating the documentation (just the info file) these error lines appear (i'm sorry for the length) and the process stops: /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:16387: Cross reference to nonexistent node `Using multiple #+TBLFM lines' (perhaps incorrect sectioning?). /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:16078: Cross reference to nonexistent node `External links' (perhaps incorrect sectioning?). /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:15548: Cross reference to nonexistent node `Code evaluation security' (perhaps incorrect sectioning?). /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:15289: Cross reference to nonexistent node `Property inheritance' (perhaps incorrect sectioning?). /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:14506: Cross reference to nonexistent node `Evaluating code blocks' (perhaps incorrect sectioning?). /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:14224: Cross reference to nonexistent node `Evaluating code blocks' (perhaps incorrect sectioning?). /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:14219: Cross reference to nonexistent node `Code evaluation security' (perhaps incorrect sectioning?). /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:14169: Cross reference to nonexistent node `Library of Babel' (perhaps incorrect sectioning?). /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:13391: Cross reference to nonexistent node `HTML export' (perhaps incorrect sectioning?). /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:12932: Cross reference to nonexistent node `Evaluating code blocks' (perhaps incorrect sectioning?). /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:12219: Cross reference to nonexistent node `Column width and alignment' (perhaps incorrect sectioning?). /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:12100: Cross reference to nonexistent node `Configuring a document converter' (perhaps incorrect sectioning?). /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:11252: Cross reference to nonexistent node `Radio targets' (perhaps incorrect sectioning?). /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:10788: Cross reference to nonexistent node `Export settings' (perhaps incorrect sectioning?). /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:10503: Cross reference to nonexistent node `In-buffer settings' (perhaps incorrect sectioning?). /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:10348: Cross reference to nonexistent node `Literal examples' (perhaps incorrect sectioning?). /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:10177: Cross reference to nonexistent node `Math formatting in HTML export' (perhaps incorrect sectioning?). /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:10017: Cross reference to nonexistent node `Generating an index' (perhaps incorrect sectioning?). /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:9922: Cross reference to nonexistent node `Text areas in HTML export' (perhaps incorrect sectioning?). /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:9850: Cross reference to nonexistent node `Plain lists' (perhaps incorrect sectioning?). /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:9613: Cross reference to nonexistent node `Document structure' (perhaps incorrect sectioning?). /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:8779: Cross reference to nonexistent node `Filtering/limiting agenda items' (perhaps incorrect sectioning?). /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:8134: Cross reference to nonexistent node `Property inheritance' (perhaps incorrect sectioning?). /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:8012: Cross reference to nonexistent node `Agenda commands' (perhaps incorrect sectioning?). /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:7816: Cross reference to nonexistent node `Agenda commands' (perhaps incorrect sectioning?). /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:7719: Cross reference to nonexistent node `Matching tags and properties' (perhaps incorrect sectioning?). /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:7197: Cross reference to nonexistent node `Adding hyperlink types' (perhaps incorrect sectioning?). /home/vicente/descarga/org-master-git-20140707/or
Re: [O] Cannot build documentation (release_8.3beta-155-g82b64d)
ing
tags and properties' (perhaps incorrect sectioning?).
/home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:7197:
Cross reference to nonexistent node `Adding
hyperlink types' (perhaps incorrect sectioning?).
/home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:6738:
Cross reference to nonexistent node `Agenda
column view' (perhaps incorrect sectioning?).
/home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:5824:
Cross reference to nonexistent node `Custom time
format' (perhaps incorrect sectioning?).
/home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:5701:
Cross reference to nonexistent node `Using the
property API' (perhaps incorrect sectioning?).
/home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:5342:
Cross reference to nonexistent node `Matching tags and
properties' (perhaps incorrect sectioning?).
/home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:5099:
Cross reference to nonexistent node `Matching
tags and properties' (perhaps incorrect sectioning?).
/home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:4327:
Cross reference to nonexistent node `Clocking
work time' (perhaps incorrect sectioning?).
/home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:3990:
Cross reference to nonexistent node `TODO
extensions' (perhaps incorrect sectioning?).
/home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:3971:
Cross reference to nonexistent node `Fast access to TODO
states' (perhaps incorrect sectioning?).
/home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:3854:
Cross reference to nonexistent node `Handling
links' (perhaps incorrect sectioning?).
/home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:2535:
Cross reference to nonexistent node `Formula syntax
for Calc' (perhaps incorrect sectioning?).
/home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:1917:
Cross reference to nonexistent node `Embedded
@LaTeX{}' (perhaps incorrect sectioning?).
/home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:1421:
Cross reference to nonexistent node `Plain
lists' (perhaps incorrect sectioning?).
/home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:1354:
Cross reference to nonexistent node `Speeding up
your agendas' (perhaps incorrect sectioning?).
/home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:1340:
Cross reference to nonexistent node `Properties
and columns' (perhaps incorrect sectioning?).
makeinfo: Removing output file `org' due to errors; use --force to preserve.
make[1]: *** [org] Error 1
make[1]: Leaving directory
`/home/vicente/descarga/org-master-git-20140804/org-mode/doc'
make: *** [info] Error 2
2014-08-01 15:43 GMT-04:00 Vicente Vera :
> Hello, recently I tried to install the latest development snapshot from
> Git through the following procedure, which has worked for me perfectly
> until now:
>
> - make cleanall
> - make up0
> - make install
>
> When the build system gets to creating the documentation (just the info
> file) these error lines appear (i'm sorry for the length) and the process
> stops:
>
> /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:16387:
> Cross reference to nonexistent node `Using
> multiple #+TBLFM lines' (perhaps incorrect sectioning?).
> /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:16078:
> Cross reference to nonexistent node `External
> links' (perhaps incorrect sectioning?).
> /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:15548:
> Cross reference to nonexistent node `Code evaluation
> security' (perhaps incorrect sectioning?).
> /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:15289:
> Cross reference to nonexistent node `Property
> inheritance' (perhaps incorrect sectioning?).
> /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:14506:
> Cross reference to nonexistent node `Evaluating code
> blocks' (perhaps incorrect sectioning?).
> /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:14224:
> Cross reference to nonexistent node `Evaluating
> code blocks' (perhaps incorrect sectioning?).
> /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:14219:
> Cross reference to nonexistent node `Code
> evaluation security' (perhaps incorrect sectioning?).
> /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:14169:
> Cross reference to nonexistent node `Library
> of Babel' (perhaps incorrect sectioning?).
> /home/vicente/descarga/org-master-git-20140707/org-mode/doc//org.texi:13391:
> Cross reference t
Re: [O] Cannot build documentation (release_8.3beta-155-g82b64d)
Yes, i had an old makeinfo (4.13) that lives in the debian wheezy repository. Just now got the latest version and it worked. Didn't thought about this since some commits ago the documentation was built just fine with makeinfo 4.13. Thank you very much Nick & Achim. 2014-08-05 12:33 GMT-04:00 Vicente Vera : > Hello. Started another "clean" cloned local repository to try building the > documentation again and the errors persist. > 'M-x org-version' gives: Org-mode version 8.3beta > (release_8.3beta-167-g003edd @ /usr/local/share/emacs/site-lisp/org/). I > installed everything except documentation. > Here's the output of 'make doc': > > make -C doc info > make[1]: Entering directory > `/home/vicente/descarga/org-master-git-20140804/org-mode/doc' > makeinfo --no-split org.texi -o org > /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:16382: > Cross reference to nonexistent node `Using > > multiple #+TBLFM lines' (perhaps incorrect sectioning?). > /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:16073: > Cross reference to nonexistent node `External > links' (perhaps incorrect sectioning?). > /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:15543: > Cross reference to nonexistent node `Code evaluation > security' (perhaps incorrect sectioning?). > /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:15284: > Cross reference to nonexistent node `Property > inheritance' (perhaps incorrect sectioning?). > /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:14501: > Cross reference to nonexistent node `Evaluating code > blocks' (perhaps incorrect sectioning?). > /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:14219: > Cross reference to nonexistent node `Evaluating > > code blocks' (perhaps incorrect sectioning?). > /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:14214: > Cross reference to nonexistent node `Code > > evaluation security' (perhaps incorrect sectioning?). > /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:14164: > Cross reference to nonexistent node `Library > > of Babel' (perhaps incorrect sectioning?). > /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:13386: > Cross reference to nonexistent node `HTML > export' (perhaps incorrect sectioning?). > /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:12927: > Cross reference to nonexistent node `Evaluating > > code blocks' (perhaps incorrect sectioning?). > /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:12214: > Cross reference to nonexistent node `Column width and > alignment' (perhaps incorrect sectioning?). > /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:12095: > Cross reference to nonexistent node `Configuring a > > document converter' (perhaps incorrect sectioning?). > /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:11247: > Cross reference to nonexistent node `Radio > targets' (perhaps incorrect sectioning?). > /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:10783: > Cross reference to nonexistent node `Export > settings' (perhaps incorrect sectioning?). > /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:10499: > Cross reference to nonexistent node `In-buffer > settings' (perhaps incorrect sectioning?). > /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:10344: > Cross reference to nonexistent node `Literal > examples' (perhaps incorrect sectioning?). > /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:10173: > Cross reference to nonexistent node `Math formatting in > > HTML export' (perhaps incorrect sectioning?). > /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:10013: > Cross reference to nonexistent node `Generating > > an index' (perhaps incorrect sectioning?). > /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:9918: > Cross reference to nonexistent node `Text > > areas in HTML export' (perhaps incorrect sectioning?). > /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:9846: > Cross reference to nonexistent node `Plain > lists' (perhaps incorrect sectioning?). > /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:9609: > Cross reference to nonexistent node `Document > structure' (perhaps incorrect sectioning?). > /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:8779: &g
Re: [O] Cannot build documentation (release_8.3beta-155-g82b64d)
I think you're right. It seems TeX Live 2014 installed its own texinfo over the one i got from the debian stable repository, but i'm not 100% sure. Thanks for the help! 2014-08-05 19:37 GMT-04:00 Vicente Vera : > Yes, i had an old makeinfo (4.13) that lives in the debian wheezy > repository. Just now got the latest version and it worked. Didn't thought > about this since some commits ago the documentation was built just fine > with makeinfo 4.13. > > Thank you very much Nick & Achim. > > > 2014-08-05 12:33 GMT-04:00 Vicente Vera : > > Hello. Started another "clean" cloned local repository to try building the >> documentation again and the errors persist. >> 'M-x org-version' gives: Org-mode version 8.3beta >> (release_8.3beta-167-g003edd @ /usr/local/share/emacs/site-lisp/org/). I >> installed everything except documentation. >> Here's the output of 'make doc': >> >> make -C doc info >> make[1]: Entering directory >> `/home/vicente/descarga/org-master-git-20140804/org-mode/doc' >> makeinfo --no-split org.texi -o org >> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:16382: >> Cross reference to nonexistent node `Using >> >> multiple #+TBLFM lines' (perhaps incorrect sectioning?). >> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:16073: >> Cross reference to nonexistent node `External >> links' (perhaps incorrect sectioning?). >> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:15543: >> Cross reference to nonexistent node `Code evaluation >> security' (perhaps incorrect sectioning?). >> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:15284: >> Cross reference to nonexistent node `Property >> inheritance' (perhaps incorrect sectioning?). >> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:14501: >> Cross reference to nonexistent node `Evaluating code >> blocks' (perhaps incorrect sectioning?). >> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:14219: >> Cross reference to nonexistent node `Evaluating >> >> code blocks' (perhaps incorrect sectioning?). >> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:14214: >> Cross reference to nonexistent node `Code >> >> evaluation security' (perhaps incorrect sectioning?). >> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:14164: >> Cross reference to nonexistent node `Library >> >> of Babel' (perhaps incorrect sectioning?). >> >> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:13386: >> Cross reference to nonexistent node `HTML >> export' (perhaps incorrect sectioning?). >> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:12927: >> Cross reference to nonexistent node `Evaluating >> >> code blocks' (perhaps incorrect sectioning?). >> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:12214: >> Cross reference to nonexistent node `Column width and >> alignment' (perhaps incorrect sectioning?). >> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:12095: >> Cross reference to nonexistent node `Configuring a >> >> document converter' (perhaps incorrect sectioning?). >> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:11247: >> Cross reference to nonexistent node `Radio >> targets' (perhaps incorrect sectioning?). >> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:10783: >> Cross reference to nonexistent node `Export >> settings' (perhaps incorrect sectioning?). >> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:10499: >> Cross reference to nonexistent node `In-buffer >> settings' (perhaps incorrect sectioning?). >> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:10344: >> Cross reference to nonexistent node `Literal >> examples' (perhaps incorrect sectioning?). >> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:10173: >> Cross reference to nonexistent node `Math formatting in >> >> HTML export' (perhaps incorrect sectioning?). >> >> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:10013: >> Cross reference to nonexistent node `Generating >> >> an index' (perhaps incorrect sectioning?). >> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//or
[O] Undocumented command: org-table-blank-field (C-c SPC)
Hello. I was browsing Emacs StackExchange and found this question: https://emacs.stackexchange.com/questions/15/how-to-clear-a-cell-in-an-org-mode-table. One of the answers mentions the org-table-blank-field command and that "For some reason it's missing from the manual.". I'm using Org release_8.3beta-580-g787733 and yes, it is not mentioned in the Tables section, nor in the indexes. It might be a good idea to document this. I would do it myself but haven't got my head around submiting patches, filling papers (although is not always necessary?), but I might, if nobody has the time. I don't want this message to be understood as a demand.
[O] Export backends are loaded after code block evaluation
Org-mode version 8.3beta (release_8.3beta-584-g3953cb @ /usr/local/share/emacs/site-lisp/org/) GNU Emacs 25.0.50.1 (i686-pc-linux-gnu, GTK+ Version 3.14.4) of 2014-11-17 Hello. Just noticed that after evaluating a code block with C-c C-c (org-babel-execute-src-block?) all export backends stored in 'org-export-backends' are loaded---or 'required'---automatically. Once I commented out my 'org-export-backends' setup those backends weren't loaded, but the default ones did (ascii html icalendar latex). Is this the intended behavior? Tried to grep my way through Org's source files looking for a clue with no success. Also, is there a way to prevent this from happening? It doesn't seem extremely necessary to me.
Re: [O] Export backends are loaded after code block evaluation
Nope, no harm has been done. Still curious about it though. IMO, there's no reference to 'ox.el' in the babel source files so I don't understand how is this possible. 2014-11-23 13:36 GMT-03:00 Nicolas Goaziou : > Hello, > > Vicente Vera writes: > >> Hello. Just noticed that after evaluating a code block with C-c C-c >> (org-babel-execute-src-block?) all export backends stored in >> 'org-export-backends' are loaded---or 'required'---automatically. Once >> I commented out my 'org-export-backends' setup those backends weren't >> loaded, but the default ones did (ascii html icalendar latex). >> >> Is this the intended behavior? > > `org-babel-execute-src-block' probably requires "ox.el" or some > back-end, triggering. Back-ends are loaded as soon as "ox.el" is > required. > >> Tried to grep my way through Org's source files looking for a clue >> with no success. >> >> Also, is there a way to prevent this from happening? It doesn't seem >> extremely necessary to me. > > It doesn't really hurt either. > > > Regards, > > -- > Nicolas Goaziou
Re: [O] Export backends are loaded after code block evaluation
Ok, finally sorted it out.
Babel doesn't load ox-* files by itself (except for ob-haskell &
ob-latex). But, in my case, the code block's result is a table. In
consequence Org needs org-table which in turn requires some ox- files
and THEN org.el evaluates (after ox.el) 'org-export-backends'.
Thank you for your patience. Now I can sleep soundly.
2014-11-24 16:42 GMT-03:00 Nicolas Goaziou :
> Vicente Vera writes:
>
>> Nope, no harm has been done. Still curious about it though. IMO,
>> there's no reference to 'ox.el' in the babel source files so I don't
>> understand how is this possible.
>
> See line 848 in "org.el" (master branch, if it matters).
>
> Basically, Babel requires an export backend ("ox-latex.el", likely),
> which, in turn requires "ox.el". The snippet above does the rest.
>
> Regards,
Re: [O] Undocumented command: org-table-blank-field (C-c SPC)
Great, thank you. I'll start looking into how could I send patches (I'm more of a 'clone/pull' Git user). 2014-12-01 13:05 GMT-03:00 Bastien : > Hi Vicente, > > Vicente Vera writes: > >> Hello. I was browsing Emacs StackExchange and found this question: >> https://emacs.stackexchange.com/questions/15/how-to-clear-a-cell-in-an-org-mode-table. >> One of the answers mentions the org-table-blank-field command and that >> "For some reason it's missing from the manual.". >> I'm using Org >> release_8.3beta-580-g787733 and yes, it is not mentioned in the Tables >> section, nor in the indexes. >> It might be a good idea to document this. > > I added it in the manual, thanks for the suggestion. > >> I would do it myself but haven't got my head around submiting patches, >> filling papers (although is not always necessary?), but I might, if >> nobody has the time. I don't want this message to be understood as a >> demand. > > Yes: http://orgmode.org/worg/org-contribute.html > > Thanks in advance! > > -- > Bastien
[O] latex to png not working
Hello. I'm trying to export an Org file with some basic latex code (block with "#+BEGIN_SRC latex :file block1.png" and "tex:dvipng" in "#+OPTIONS:") but this shows up in the *Messages* buffer: >org-babel-exp processing... >executing Latex code block (block1)... >Failed to create dvi file from c:/DOCUME~1/User1/CONFIG~1/Temp/orgtex1376-zt.tex >Code block evaluation complete. >Formatting LaTeX using dvipng The ODT document is created but, obviously, without the PNG formulas. It happens too with inline LaTeX fragments: >Creating LaTeX Image 1... >Failed to create dvi file from c:/DOCUME~1/User1/CONFIG~1/Temp/orgtex124_dQ.tex >Embedding c:/Documents and Settings/User1/My documents/testodt/ltxpng/testodt_0d00b93575360a27f804d102a03f4e2d4ee0f915.png as Images/0001.png... >OpenDocument export failed: Copying file: no such file or directory, c:/Documents and Settings/User1/My documents/testodt/ltxpng/testodt_0d00b93575360a27f804d102a03f4e2d4ee0f915.png, c:/DOCUME~1/User1/CONFIG~1/Temp/odt-124Zro/Images/0001.png Org's LaTeX preview doesn't work either. The dvi files are not being created. My setup includes: - Windows XP SP3 - Emacs 24.3.1 with Org 8.2.1 (20131007 from ELPA) and AUCTeX 11.87.1 (from ELPA); everything correctly (and cleanly) installed - TeX Live 2013 (full install), on Windows' PATH Standalone dvipng works ok (tried it with a small dvi file through Windows command line) and latex too (through cmd, Org---latex & pdf export--- and AUCTeX). Thanks for reading.
Re: [O] latex to png not working
The problem went away once i changed the values for both TEMP and TMP environment variables to "C:\Temp" (without quotation marks). This---i think---has to do with long filenames (path to TEMP folder). Great, great job by the way. Org makes so much things easier. Thank you very much! 2013/10/13 Vicente Vera > Hello. I'm trying to export an Org file with some basic latex code (block > with "#+BEGIN_SRC latex :file block1.png" and "tex:dvipng" in "#+OPTIONS:") > but this shows up in the *Messages* buffer: > > >org-babel-exp processing... > >executing Latex code block (block1)... > >Failed to create dvi file from > c:/DOCUME~1/User1/CONFIG~1/Temp/orgtex1376-zt.tex > >Code block evaluation complete. > >Formatting LaTeX using dvipng > > The ODT document is created but, obviously, without the PNG formulas. It > happens too with inline LaTeX fragments: > > >Creating LaTeX Image 1... > >Failed to create dvi file from > c:/DOCUME~1/User1/CONFIG~1/Temp/orgtex124_dQ.tex > >Embedding c:/Documents and Settings/User1/My > documents/testodt/ltxpng/testodt_0d00b93575360a27f804d102a03f4e2d4ee0f915.png > as Images/0001.png... > >OpenDocument export failed: Copying file: no such file or directory, > c:/Documents and Settings/User1/My > documents/testodt/ltxpng/testodt_0d00b93575360a27f804d102a03f4e2d4ee0f915.png, > c:/DOCUME~1/User1/CONFIG~1/Temp/odt-124Zro/Images/0001.png > > Org's LaTeX preview doesn't work either. The dvi files are not being > created. > > My setup includes: > - Windows XP SP3 > - Emacs 24.3.1 with Org 8.2.1 (20131007 from ELPA) and AUCTeX 11.87.1 > (from ELPA); everything correctly (and cleanly) installed > - TeX Live 2013 (full install), on Windows' PATH > > Standalone dvipng works ok (tried it with a small dvi file through Windows > command line) and latex too (through cmd, Org---latex & pdf export--- and > AUCTeX). > > Thanks for reading. >
[O] problem with titles in odt export
Hello. I think there's a problem when exporting to odt format with certain characters in #+TITLE lines. For example, exporting an org file with "ñ" (ñ in HTML) or letters with acute accents (á, ó, etc.) in the title---my document is written in spanish---results in a file with no title at all (nor author/date). Also, an error warning appears in LibreOffice when opening. The body of the document (headers, etc.) exports normally. I'm using GNU Emacs 24.3.1. Org-mode version 8.2.1 (8.2.1-15-ge5cecc-elpa @ c:/emacs/.emacs.d/elpa/org-20131021/). Thank you very much for the great work.
[O] (idea?) fontification of live code blocks
Hello. I don't know if this has been mentioned before, but it would be nice
to have fontified live code blocks, since sometimes it's hard to clearly
distinguish---at least at first sight---between regular text and something
like, for example, src_R[:session
*project2*]{round(mean(data$AGE),digits=0)}.
[O] Issues when compiling Org master from source in GNU Emacs 25.0.50.1
Hello When I started using GNU Emacs compiled from the emacs25 branch two issues come up consistently during Org make routine. These issues are related to changes in the next Emacs version. [...] Compiling /home/user/repositories/org-mode/lisp/org-src.el... In org-src-font-lock-fontify-block: org-src.el:504:54:Warning: ‘font-lock-fontify-buffer’ is for interactive use only; use ‘font-lock-ensure’ or ‘font-lock-flush’ instead. [...] Compiling /home/user/repositories/org-mode/lisp/org.el... In org-fast-tag-selection: org.el:15261:47:Error: ‘add-to-list’ can’t use lexical var ‘buffer-tags’; use ‘push’ or ‘cl-pushnew’ [...] Note that the .elc files get generated just fine, I mean, the make routine finishes correctly and Org is still usable.
Re: [O] Issues when compiling Org master from source in GNU Emacs 25.0.50.1
Hello Kyle, Thanks for your reply. I see now why `font-lock-fontify-buffer' hasn't been replaced. 2016-01-20 12:28 GMT-03:00 Kyle Meyer : > Hi Vicente, > > Vicente Vera writes: > >> Hello >> >> When I started using GNU Emacs compiled from the emacs25 branch two >> issues come up consistently during Org make routine. These issues are >> related to changes in the next Emacs version. > > Thanks for reporting these. > >> Compiling /home/user/repositories/org-mode/lisp/org-src.el... >> >> In org-src-font-lock-fontify-block: >> org-src.el:504:54:Warning: ‘font-lock-fontify-buffer’ is for interactive use >> only; use ‘font-lock-ensure’ or ‘font-lock-flush’ instead. > > This has been switched over to font-lock-ensure a couple times (in > f36b19e and then reverted in 99f, then again in d81e6b5 and reverted > in 003a0f1). When font-lock-ensure is used, source blocks don't get > highlighted. > >> Compiling /home/user/repositories/org-mode/lisp/org.el... >> >> In org-fast-tag-selection: >> org.el:15261:47:Error: ‘add-to-list’ can’t use lexical var ‘buffer-tags’; use >> ‘push’ or ‘cl-pushnew’ > > I think this one should be fixed. I'll look into it. > > -- > Kyle
[O] Tiny typo in exported LaTeX code
Hello. Just now I exported a minimal Org file to LaTeX (no fancy
stuff, just a title, two headlines and harmless text) and the date is
messed up. The offending line is:
\date{$\backslash$oday}
Org-mode version 8.3beta (release_8.3beta-1003-gfc790f @
/usr/local/share/emacs/site-lisp/org/)
GNU Emacs 24.5.1
Re: [O] Tiny typo in exported LaTeX code
Thank you!
2015-04-05 14:05 GMT-03:00 Nicolas Goaziou :
> Hello,
>
> Vicente Vera writes:
>
>> Hello. Just now I exported a minimal Org file to LaTeX (no fancy
>> stuff, just a title, two headlines and harmless text) and the date is
>> messed up. The offending line is:
>>
>> \date{$\backslash$oday}
>
> Fixed. Thank you.
>
> --
> Nicolas Goaziou
[O] [PATCH] TINYCHANGE Fix some spanish translations in ox.el
Hello. This patch fixes some spanish translations defined in
org-export-dictionary. It also adds a :default property for the
spanish "Table of Contents" entry, thus allowing ox-odt (and probably
other exporters) to correctly translate this element.
>From 668ffc388db671e56a50ab3b6a210f61a6a4755b Mon Sep 17 00:00:00 2001
From: Vicente Vera Parra
Date: Wed, 8 Apr 2015 21:12:07 -0300
Subject: [PATCH] ox: Fix spanish translations
* lisp/ox.el (org-export-dictionary): Fix spanish translations. Also
add default spanish translation for "Table of Contents".
TINYCHANGE
---
lisp/ox.el | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/lisp/ox.el b/lisp/ox.el
index 90c7e7d..45ffc4a 100644
--- a/lisp/ox.el
+++ b/lisp/ox.el
@@ -5412,7 +5412,7 @@ them."
("List of Listings"
("da" :default "Programmer")
("de" :default "Programmauflistungsverzeichnis")
- ("es" :default "Indice de Listados de programas")
+ ("es" :default "Índice de Listados de programas")
("et" :default "Loendite nimekiri")
("fr" :default "Liste des programmes")
("ja" :default "ソースコード目次")
@@ -5424,7 +5424,7 @@ them."
("List of Tables"
("da" :default "Tabeller")
("de" :default "Tabellenverzeichnis")
- ("es" :default "Indice de tablas")
+ ("es" :default "Índice de tablas")
("et" :default "Tabelite nimekiri")
("fr" :default "Liste des tableaux")
("ja" :default "表目次")
@@ -5455,7 +5455,7 @@ them."
("See section %s"
("da" :default "jævnfør afsnit %s")
("de" :default "siehe Abschnitt %s")
- ("es" :default "vea seccion %s")
+ ("es" :default "Vea sección %s")
("et" :html "Vaata peatükki %s" :utf-8 "Vaata peatükki %s")
("fr" :default "cf. section %s")
("ja" :default "セクション %s を参照")
@@ -5495,7 +5495,7 @@ them."
("da" :default "Indhold")
("de" :default "Inhaltsverzeichnis")
("eo" :default "Enhavo")
- ("es" :html "Índice")
+ ("es" :html "Índice" :default "Índice")
("et" :default "Sisukord")
("fi" :html "Sisällysluettelo")
("fr" :ascii "Sommaire" :default "Table des matières")
@@ -5518,7 +5518,7 @@ them."
("Unknown reference"
("da" :default "ukendt reference")
("de" :default "Unbekannter Verweis")
- ("es" :default "referencia desconocida")
+ ("es" :default "Referencia desconocida")
("et" :default "Tundmatu viide")
("fr" :ascii "Destination inconnue" :default "Référence inconnue")
("ja" :default "不明な参照先")
--
1.9.1
Re: [O] [PATCH] TINYCHANGE Fix some spanish translations in ox.el
Exactly. Since only some entries include the :ascii property I thought
it wouldn't hurt to omit them. Here's a more complete patch which
includes both :ascii and :html properties:
>From b7de61bb9d57b1790a7fe97d6e478542e894a9d0 Mon Sep 17 00:00:00 2001
From: Vicente Vera Parra
Date: Thu, 9 Apr 2015 11:51:54 -0300
Subject: [PATCH 2/2] ox: Fix spanish translations
* lisp/ox.el (org-export-dictionary): Fix spanish translations. Also
add default spanish translation for "Table of Contents" and
"References".
TINYCHANGE
---
lisp/ox.el | 19 ++-
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git a/lisp/ox.el b/lisp/ox.el
index 45ffc4a..d2ee7c9 100644
--- a/lisp/ox.el
+++ b/lisp/ox.el
@@ -5299,7 +5299,7 @@ them."
("zh-TW" :html "作者" :utf-8 "作者"))
("Continued from previous page"
("de" :default "Fortsetzung von vorheriger Seite")
- ("es" :default "Continúa de la página anterior")
+ ("es" :html "Continúa de la página anterior"
:ascii "Continua de la pagina anterior" :default "Continúa de la
página anterior")
("fr" :default "Suite de la page précédente")
("it" :default "Continua da pagina precedente")
("ja" :default "前ページからの続き")
@@ -5309,7 +5309,7 @@ them."
:utf-8 "(Продолжение)"))
("Continued on next page"
("de" :default "Fortsetzung nächste Seite")
- ("es" :default "Continúa en la siguiente página")
+ ("es" :html "Continúa en la siguiente página"
:ascii "Continua en la siguiente pagina" :default "Continúa en la
siguiente página")
("fr" :default "Suite page suivante")
("it" :default "Continua alla pagina successiva")
("ja" :default "次ページに続く")
@@ -5344,7 +5344,7 @@ them."
("Equation"
("da" :default "Ligning")
("de" :default "Gleichung")
- ("es" :html "Ecuación" :default "Ecuación")
+ ("es" :ascii "Ecuacion" :html "Ecuación" :default "Ecuación")
("et" :html "Võrrand" :utf-8 "Võrrand")
("fr" :ascii "Equation" :default "Équation")
("ja" :default "方程式")
@@ -5389,7 +5389,7 @@ them."
("da" :default "Fodnoter")
("de" :html "Fußnoten" :default "Fußnoten")
("eo" :default "Piednotoj")
- ("es" :html "Nota al pie de página" :default "Nota al pie
de página")
+ ("es" :ascii "Nota al pie de pagina" :html "Nota al pie de
página" :default "Nota al pie de página")
("et" :html "Allmärkused" :utf-8 "Allmärkused")
("fi" :default "Alaviitteet")
("fr" :default "Notes de bas de page")
@@ -5412,7 +5412,7 @@ them."
("List of Listings"
("da" :default "Programmer")
("de" :default "Programmauflistungsverzeichnis")
- ("es" :default "Índice de Listados de programas")
+ ("es" :ascii "Indice de Listados de programas" :html
"Índice de Listados de programas" :default "Índice de Listados
de programas")
("et" :default "Loendite nimekiri")
("fr" :default "Liste des programmes")
("ja" :default "ソースコード目次")
@@ -5424,7 +5424,7 @@ them."
("List of Tables"
("da" :default "Tabeller")
("de" :default "Tabellenverzeichnis")
- ("es" :default "Índice de tablas")
+ ("es" :ascii "Indice de tablas" :html "Índice de tablas"
:default "Índice de tablas")
("et" :default "Tabelite nimekiri")
("fr" :default "Liste des tableaux")
("ja" :default "表目次")
@@ -5451,11 +5451,12 @@ them."
("zh-CN" :html "代码%d " :utf-8 "代码%d "))
("References"
("fr" :ascii "References" :default "Références")
- ("de" :default "Quellen"))
+ ("de" :default "Quellen")
+ ("es" :default "Referencias"))
("See section %s"
("da" :default "jævnfør afsnit %s")
("de" :default "siehe Abschnitt %s")
- ("es" :default "Vea sección %s")
+ ("es" :ascii "Vea seccion %s" :html "Vea sección %s"
:default "Vea sección %s")
("et" :html "Vaata peatükki %s" :utf-8 "Vaata peatükki %s")
("fr" :default "cf. section %s")
("ja" :default "セクション %s を参照")
@@ -5495,7 +5496,7 @@ them."
("da" :default "Indhold")
("de" :default "Inhaltsverzeichnis")
("eo" :default "Enhavo")
- ("es" :html "Índice" :default "Índice")
+ ("es" :ascii "Indice" :html "Índice" :default "Índice")
("et" :default "Sisukord")
("fi" :html "Sisällysluettelo")
("fr" :ascii "Sommaire" :default "Table des matières")
--
1.9.1
[O] Error when using org-ctrl-c-ctrl-c to add tags
Hello. This shows up when trying to add tags to a headline with org-ctrl-c-ctrl-c: apply: Wrong type argument: listp, org-tags-completion-function Org-mode version 8.3beta (release_8.3beta-1045-gd8494b @ /usr/local/share/emacs/site-lisp/org/) GNU Emacs 24.5.50.1 (i686-pc-linux-gnu, GTK+ Version 3.4.2)
Re: [O] Error when using org-ctrl-c-ctrl-c to add tags
Hi. Don't think there are more details to provide. The error message appears upon pressing C-c C-c (bound to the org-ctrl-c-ctrl-c command) on a headline, doesn't matter which level. It happened in 3 different Org files, one of which was created for testing. Also tried with "emacs -q" but the error persisted. Strange message though, org-tags-completion-function is a function, not a variable, so why is Emacs complaining that it isn't a list? Probably related to commit acf7f47ecd20a48c05f97dc660b00d1850b57e10?
Re: [O] Error when using org-ctrl-c-ctrl-c to add tags
Hello Marc. Yes, upon further inspection it seems the problem is in org-icompleting-read. This function is complaining that org-tags-completion--function---one of its arguments---is not a list. 2015-04-19 11:36 GMT-03:00 Marc Ihm : > Vicente Vera writes: > >> Hi. >> Don't think there are more details to provide. The error message >> appears upon pressing C-c C-c (bound to the org-ctrl-c-ctrl-c command) >> on a headline, doesn't matter which level. >> It happened in 3 different Org files, one of which was created for testing. >> Also tried with "emacs -q" but the error persisted. >> >> Strange message though, org-tags-completion-function is a function, >> not a variable, so why is Emacs complaining that it isn't a list? >> Probably related to commit acf7f47ecd20a48c05f97dc660b00d1850b57e10? > > I see this error too; the patch below fixes it for me (and corrects the > nexting level of 'completing-read too ...) > > best regards > Marc > > > diff --git a/lisp/org.el b/lisp/org.el > index 8a00847..f440382 100755 > --- a/lisp/org.el > +++ b/lisp/org.el > @@ -10512,10 +10512,11 @@ from." > (listp (second args))) > 'org-iswitchb-completing-read) > (t (or (and (boundp 'completing-read-function) > - completing-read-function) > - 'completing-read))) > + completing-read-function)) > + 'completing-read)) >(concat (car args)) > - (if (consp (car (nth 1 args))) > + (if (and (consp (nth 1 args)) > + (consp (car (nth 1 args > (mapcar 'car (nth 1 args)) > (nth 1 args)) >(cddr args)
Re: [O] Error when using org-ctrl-c-ctrl-c to add tags
Worked for me. 2015-04-19 13:05 GMT-03:00 Marc Ihm : > > Okay, this one only tries to fix, what seems broken ... > Could someone please check ? > > best regards > Marc > > > diff --git a/lisp/org.el b/lisp/org.el > index 24b3a69..8a00847 100755 > --- a/lisp/org.el > +++ b/lisp/org.el > @@ -10515,8 +10515,7 @@ from." > completing-read-function) >'completing-read))) >(concat (car args)) > - (if (and (consp (nth 1 args)) > - (consp (car (nth 1 args > + (if (consp (car (nth 1 args))) > (mapcar 'car (nth 1 args)) > (nth 1 args)) >(cddr args)
[O] [release_8.3beta-1062-gce4e64] Error when exporting to ODT
Hello list. Just tried to export an Org file to ODT but this error appeared (taken from the Messages buffer): ... LaTeX to MathML converter not available. Formatting LaTeX using verbatim OpenDocument export failed: Assertion failed: (funcall predicate element info) Tried with a MWE and with a minimal init.el (because of org-export-backends and the "odt" symbol) but the error persists. Org and Emacs version: Org-mode version 8.3beta (release_8.3beta-1062-gce4e64 @ /usr/local/share/emacs/site-lisp/org/) GNU Emacs 24.5.50.1 (i686-pc-linux-gnu, GTK+ Version 3.4.2)
Re: [O] [release_8.3beta-1062-gce4e64] Error when exporting to ODT
The patch works. Thank you. About 2bdc661fde75ed226b19c802ecd31ce12d2ec7e1, I don't use latexmlmath so can't comment on that.
[O] [PATCH] TINYCHANGE Allow attaching SVG images by default in exported ODT documents
Hello list.
The patch below changes org-odt-inline-image-rules value, thus
allowing exported ODT documents to include SVG images by default.
From 991f4add7c644902bd6bcd2a5b9eb01e1ea5ade9 Mon Sep 17 00:00:00 2001
From: Vicente Vera Parra
Date: Mon, 27 Apr 2015 18:02:22 -0300
Subject: [PATCH] ox-odt: Allow attaching SVG images by default
* lisp/ox-odt.el (org-odt-inline-image-rules): Modify default rule to
allow including inline SVG images in exported ODT documents.
TINYCHANGE
---
lisp/ox-odt.el | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lisp/ox-odt.el b/lisp/ox-odt.el
index faf0b1c..444c1b7 100644
--- a/lisp/ox-odt.el
+++ b/lisp/ox-odt.el
@@ -765,7 +765,7 @@ link's path."
:value-type (regexp :tag "Path")))
(defcustom org-odt-inline-image-rules
- '(("file" . "\\.\\(jpeg\\|jpg\\|png\\|gif\\)\\'"))
+ '(("file" . "\\.\\(jpeg\\|jpg\\|png\\|gif\\|svg\\)\\'"))
"Rules characterizing image files that can be inlined into ODT.
A rule consists in an association whose key is the type of link
--
1.9.1
Re: [O] Installing from Git
Hello. This is my Org-from-Git recipe: After you've cloned the repository (master branch), run "make" and then edit the "local.mk" file. There you'll find a variable named "prefix"; change it according to your Emacs installation. In my setup, Emacs files live in /usr/share/emacs/ so I leave "prefix" unchanged. In a previous installation it was in /usr/local/share/emacs/ so I wrote "prefix = /usr/local/share". Only then run "make install". Now the Info manual will be correctly installed. Also important, add this line to your init file: (require 'org-loaddefs) That should do it.
Re: [O] Trouble with autofill mode
Hello, This StackExchange question might help you out: https://emacs.stackexchange.com/questions/12392/prevent-fill-paragraph-from-breaking-latex-citations-in-org-mode (Only if I got your question right...)
[O] PNG R plots size
Hello. I have a source code block for an R plot with the following header: #+BEGIN_SRC R :results output graphics :file figure1.png :exports results It works, but the default size is too small. When I change the extension to SVG or PDF (i.e. when exporting to LaTeX, but is not what i need right now) the dimensions are fine. How can I control the size of a PNG graphic? Do I need to tweak something inside Org or specify something in R? Thanks.
[O] org-babel-capitalize-example-region-markers
Hello. Just noticed that example block headings wrapping code evaluation results appear downcased (arrows added): #+RESULTS: #+begin_example <= ... some result... #+end_example <= In ob-core.el, line 2438 there's a "hidden" variable that controls wether the headings appear upcased: ‘org-babel-capitalize-example-region-markers’. Setting it to non-nil seems to solve the "problem". Shouldn't this variable be public through the customize interface? Also, it seems "capitalize" is the wrong verb here?
Re: [O] org-babel-capitalize-example-region-markers
Nice, thank you. 2017-01-27 1:12 GMT+00:00 Kyle Meyer : > Kyle Meyer writes: > > [...] > > > Here's a patch. I'll apply it to master in a day or two if there are no > > objections. > > Applied with 9c111f63 (with :version changed from 25.2 to 26.1). > > -- > Kyle >
[O] Exporting blocks of text completely verbatim
Hello. This discussion https://lists.gnu.org/archive/html/emacs-orgmode/2017-02/msg00163.html points out that Org tables are converted to HTML tables when exporting through "ox-md". Leaving Markdown-related issues aside, I've stumbled upon this problem a while back. It is suggested that wrapping the table within a "#+(BEGIN|END)_EXPORT md" should leave it as-is in the exported document but that is not the case. The table gets converted to HTML anyway. When skimming through the Org manual I found that "#+(BEGIN|END)_EXPORT back-end" blocks are used to export text *only* for the specified back-end. This appears in the ASCII back-end documentation (does it work like this for others back-ends?). In a general level, is there a way to keep blocks of text completely unmodified (without indentation also) on export?
Re: [O] Exporting blocks of text completely verbatim
Hmm nope. Still some modifications are introduced depending on the back-end. Example blocks are generally indented. There are cases where those changes makes sense such as in HTML export but for ASCII and ASCII-based markups truly verbatim blocks would make sense I believe. For example, one could edit an Org document and keep some text blocks completely unchanged so later another processing tool (such as Pandoc) could deal with them accordingly. 2017-02-09 14:27 GMT+00:00 John Kitchin : > Isn't > > #+BEGIN_EXAMPLE > Long block > #+END_EXAMPLE > > what you want? > > John > > --- > Professor John Kitchin > Doherty Hall A207F > Department of Chemical Engineering > Carnegie Mellon University > Pittsburgh, PA 15213 > 412-268-7803 > @johnkitchin > http://kitchingroup.cheme.cmu.edu > > > On Thu, Feb 9, 2017 at 3:11 PM, Vicente Vera wrote: > >> Hello. This discussion >> https://lists.gnu.org/archive/html/emacs-orgmode/2017-02/msg00163.html >> points out that Org tables are converted to HTML tables when exporting >> through "ox-md". Leaving Markdown-related issues aside, I've stumbled >> upon this problem a while back. >> >> It is suggested that wrapping the table within a "#+(BEGIN|END)_EXPORT >> md" should leave it as-is in the exported document but that is not the >> case. The table gets converted to HTML anyway. >> >> When skimming through the Org manual I found that >> "#+(BEGIN|END)_EXPORT back-end" blocks are used to export text *only* >> for the specified back-end. This appears in the ASCII back-end >> documentation (does it work like this for others back-ends?). >> >> In a general level, is there a way to keep blocks of text completely >> unmodified (without indentation also) on export? >> >> >
Re: [O] Exporting blocks of text completely verbatim
You're absolutely right. The MWE I made had a nasty typo that blew everything up! I'm sorry for the noise. The information in the manual still looks misleading to me: #+BEGIN_EXPORT ascii All lines in this block will appear only when using this back-end. #+END_EXPORT (Taken from "12.7 ASCII/Latin-1/UTF-8 export") This doesn't seem to be related to verbatim text. 2017-02-09 19:19 GMT+00:00 Charles C. Berry : > On Thu, 9 Feb 2017, Vicente Vera wrote: > > Hello. This discussion >> https://lists.gnu.org/archive/html/emacs-orgmode/2017-02/msg00163.html >> points out that Org tables are converted to HTML tables when exporting >> through "ox-md". Leaving Markdown-related issues aside, I've stumbled >> upon this problem a while back. >> >> It is suggested that wrapping the table within a "#+(BEGIN|END)_EXPORT >> md" should leave it as-is in the exported document but that is not the >> case. The table gets converted to HTML anyway. >> >> > Not in recent versions of org. Here is an example of a table that is > exported as a table without any html-ization: > > #+BEGIN_SRC emacs-lisp :results raw > (org-export-string-as >" > ,#+begin_export md > | a | > | b | > ,#+end_export" >'md t) > > #+END_SRC > > #+RESULTS: > | a | > | b | > > > Of course, the comma escapes are stripped before `org-export-string-as' > sees the string. > > HTH, > > Chuck >
[O] Strings converted to numbers in Org table?
Hello. I'm trying to get an Org table from an R data frame but data is
lost in the process.
Here is a MWE. Note that:
- In R every value is a string. "var2" contains no numbers (is a
character vector).
- Upon conversion to a table Org removes the zero from "var2" last
value.
--
#+BEGIN_SRC R :session *mwe* :results value table :colnames yes
tst <- data.frame(var1 = c("a", "b", "c", "d", "e", "f", "g"),
var2 = c("150", "210", "140", "150", "192", "497",
"3.350"),
stringsAsFactors = FALSE)
tst
#+END_SRC
#+RESULTS:
| var1 | var2 |
|--+--|
| a| 150 |
| b| 210 |
| c| 140 |
| d| 150 |
| e| 192 |
| f| 497 |
| g| 3.35 |
--
Here's the output as seen in R:
: > tst
: var1 var2
: 1a 150
: 2b 210
: 3c 140
: 4d 150
: 5e 192
: 6f 497
: 7g 3.350
Details on the data frame:
: > str(tst)
: 'data.frame':7 obs. of 2 variables:
: $ var1: chr "a" "b" "c" "d" ...
: $ var2: chr "150" "210" "140" "150" ...
It seems Org knows that the values on column "var2" are numbers and
converts the strings to numbers, applying some obscure trimming on the
digits. The "3.350" value needs to be left as is.
Re: [O] Strings converted to numbers in Org table?
Probably the issue is related to this function in `ob-core.el'?
org-babel-read: "Convert the string value of CELL to a number if
appropriate."
Behind the curtains lies the built-in function `string-to-number'.
Maybe that conversion should be made optional to leave the strings
untouched.
2017-02-24 1:40 GMT+00:00 Vicente Vera :
> Hello. I'm trying to get an Org table from an R data frame but data is
> lost in the process.
>
> Here is a MWE. Note that:
>
> - In R every value is a string. "var2" contains no numbers (is a
> character vector).
>
> - Upon conversion to a table Org removes the zero from "var2" last
> value.
>
> --
>
> #+BEGIN_SRC R :session *mwe* :results value table :colnames yes
> tst <- data.frame(var1 = c("a", "b", "c", "d", "e", "f", "g"),
> var2 = c("150", "210", "140", "150", "192", "497",
> "3.350"),
> stringsAsFactors = FALSE)
> tst
> #+END_SRC
>
> #+RESULTS:
> | var1 | var2 |
> |--+--|
> | a| 150 |
> | b| 210 |
> | c| 140 |
> | d| 150 |
> | e| 192 |
> | f| 497 |
> | g| 3.35 |
>
> --
>
> Here's the output as seen in R:
>
> : > tst
> : var1 var2
> : 1a 150
> : 2b 210
> : 3c 140
> : 4d 150
> : 5e 192
> : 6f 497
> : 7g 3.350
>
> Details on the data frame:
>
> : > str(tst)
> : 'data.frame':7 obs. of 2 variables:
> : $ var1: chr "a" "b" "c" "d" ...
> : $ var2: chr "150" "210" "140" "150" ...
>
> It seems Org knows that the values on column "var2" are numbers and
> converts the strings to numbers, applying some obscure trimming on the
> digits. The "3.350" value needs to be left as is.
>
>
Re: [O] Strings converted to numbers in Org table?
Hello again, I'm sorry for being noisy.
OK yes, `org-babel-read' is indeed converting "number strings" to
numbers.
Basically this is what happens:
: (string-to-number "3.350") => 3.35
To leave cell values unchanged I did this clumsy hack:
#+BEGIN_SRC emacs-lisp
(defun test-other-org-babel-read (cell &optional inhibit-lisp-eval)
(if (and (stringp cell) (not (equal cell "")))
;; ;; (or (org-babel--string-to-number cell)
(if (and (not inhibit-lisp-eval)
(or (member (substring cell 0 1) '("(" "'" "`" "["))
(string= cell "*this*")))
(eval (read cell) t)
(if (string= (substring cell 0 1) "\"")
(read cell)
(progn (set-text-properties 0 (length cell) nil cell) cell)))
;; ;; )
cell))
;; Override default behavior
(fset 'org-babel-read 'test-other-org-babel-read)
#+END_SRC
It would be useful to have a header argument to prevent this
conversion. Probably somebody else has had the same issue?
2017-02-27 13:49 GMT+00:00 Vicente Vera :
> Probably the issue is related to this function in `ob-core.el'?
>
> org-babel-read: "Convert the string value of CELL to a number if
> appropriate."
>
> Behind the curtains lies the built-in function `string-to-number'.
>
> Maybe that conversion should be made optional to leave the strings
> untouched.
>
> 2017-02-24 1:40 GMT+00:00 Vicente Vera :
>
>> Hello. I'm trying to get an Org table from an R data frame but data is
>> lost in the process.
>>
>> Here is a MWE. Note that:
>>
>> - In R every value is a string. "var2" contains no numbers (is a
>> character vector).
>>
>> - Upon conversion to a table Org removes the zero from "var2" last
>> value.
>>
>> --
>>
>> #+BEGIN_SRC R :session *mwe* :results value table :colnames yes
>> tst <- data.frame(var1 = c("a", "b", "c", "d", "e", "f", "g"),
>> var2 = c("150", "210", "140", "150", "192", "497",
>> "3.350"),
>> stringsAsFactors = FALSE)
>> tst
>> #+END_SRC
>>
>> #+RESULTS:
>> | var1 | var2 |
>> |--+--|
>> | a| 150 |
>> | b| 210 |
>> | c| 140 |
>> | d| 150 |
>> | e| 192 |
>> | f| 497 |
>> | g| 3.35 |
>>
>> --
>>
>> Here's the output as seen in R:
>>
>> : > tst
>> : var1 var2
>> : 1a 150
>> : 2b 210
>> : 3c 140
>> : 4d 150
>> : 5e 192
>> : 6f 497
>> : 7g 3.350
>>
>> Details on the data frame:
>>
>> : > str(tst)
>> : 'data.frame':7 obs. of 2 variables:
>> : $ var1: chr "a" "b" "c" "d" ...
>> : $ var2: chr "150" "210" "140" "150" ...
>>
>> It seems Org knows that the values on column "var2" are numbers and
>> converts the strings to numbers, applying some obscure trimming on the
>> digits. The "3.350" value needs to be left as is.
>>
>>
>
Re: [O] Strings converted to numbers in Org table?
Yes, it is a rare case indeed. It's not necessary nor appropiate to change Babel's behavior. Long story short, I'm building several LaTeX tables from CSV files which in turn come from Excel files. I'm not the author of these Excel files and I have to reproduce them as faithful as possible. The problem is that a comma is used as a decimal mark instead of a dot. `string-to-number' correctly interprets numbers such as "1.100" as floating point. But in this particular case this is not the expected behavior and the tables get messed up. Your solution is a much better option. Thanks. 2017-02-27 17:33 GMT+00:00 Nicolas Goaziou : > Hello, > > Vicente Vera writes: > > > It would be useful to have a header argument to prevent this > > conversion. Probably somebody else has had the same issue? > > Since this case may be rare, what about inserting a non breaking > zero-width space right before 3.350? > > Regards, > > -- > Nicolas Goaziou >
Re: [O] resize org-table when exporting to latex
This requires some LaTeX plumbing work. A few tricks:
First, use tabularx as suggested to stretch the columns automatically as
the size of the table changes.
- Use a smaller font size, such as :font \scriptsize
- Enlarge the table horizontally (for example: :width 0.8\paperheight)
- Put the page in landscape with the "pdflscape" package: wrap the table
with "#+BEGIN_landscape ... #+END_landscape" and change :width to
\paperheight
- Use package "graphicx" and wrap the table in "#+LATEX:
\resizebox{0.8\paperheight}{!}{ ... #+LATEX: }" to make the whole table
smaller
An example of the above in Org syntax (remember to call the necessary
packages):
#+BEGIN_landscape
#+ATTR_LATEX: :options [htbp]
#+BEGIN_table
#+BEGIN_center
#+LATEX: \resizebox{0.8\paperheight}{!}{
#+CAPTION: A big table made small
#+BEGIN_threeparttable
#+ATTR_LATEX: :center nil :environment tabularx :width \paperheight :align
:font \scriptsize :booktabs t
...
#+ATTR_LATEX: :options [flushleft]
#+BEGIN_tablenotes
\item[] Source: Someone on the Internet.
#+END_tablenotes
#+END_threeparttable
#+LATEX: }
#+END_center
#+END_table
#+END_landscape
2017-02-28 0:21 GMT+00:00 Jeremie Juste :
>
> Hello,
>
> Is there a way to resize latex table when exporting to latex?
> For now my only recourse is to export the latex table copy the latex
> code back to org-mode apply \scalebox.
>
> Do you have a more convenient way in mind?
>
> Best wishes,
>
> Jeremie
>
>
>
>
>
>
>
Re: [O] Complex conversion of text to org table
Hello. In this case Org splits into columns everytime it sees a space, so "baking soda" ends up in two columns. A brute force solution: replace the spaces between words that shouldn't be put into separated columns with an underscore: 1_cup all-purpose_flour Convert it to an Org table and then do a quick M-x replace-string to replace '_' with ' '. 2017-03-12 15:14 GMT+00:00 Xebar Saram : > Hi list > > so im trying to use orgmode to collect food recepies. i have one issue > which is to convert text based ingridents list into org tables. > > for example take this list > > 3/4 cup milk > 2 tablespoons white vinegar > 1 cup all-purpose flour > 2 tablespoons white sugar > 1 teaspoon baking powder > 1/2 teaspoon baking soda > 1/2 teaspoon salt > 1 egg > 2 tablespoons butter, melted > cooking spray > > if i mark this as a region and issue `org-table-create-or-convert-from-region` > this is the result > > | 3/4 | cup | milk| | || | > | | > | 2 | tablespoons | white | vinegar | (%or | better | yet | > lemon | juice%) | > | 1 | cup | all-purpose | flour | || | > | | > | 2 | tablespoons | white | sugar | || | > | | > | 1 | teaspoon| baking | powder | || | > | | > | 1/2 | teaspoon| baking | soda| || | > | | > | 1/2 | teaspoon| salt| | || | > | | > | 1 | egg | | | || | > | | > | 2 | tablespoons | butter, | melted | || | > | | > | cooking | spray | | | || | > | | > > > as you can see it got the amount (1/2) and the unit (cup) right yet the > actual ingredients is cut into several columns > > i dont really know how to deal with this. is there a more intelligent way > of auto directing the conversion to split it the correct way? > > if not any suggestions on how to convert it in a better way? perhaps a > command to quick delete the separator (|) across all the column? > > thx alot in advance > > Z >
Re: [O] Complex conversion of text to org table
OK that's a nice trick. Very useful for CSV files. Thanks! 2017-03-12 16:52 GMT+00:00 Scott Randby : > On 03/12/2017 11:35 AM, Xebar Saram wrote: > > Thx Vicente! > > > > Thats a decent idea. can this be all wrapped in a function (i have zero > > coding skills :)) ? i have hundreds of these tables to convert :) > > > > best! > > > > Z > > OR > > 3/4, cup, milk > 2, tablespoons, white vinegar > 1, cup, all-purpose flour > 2, tablespoons, white sugar > 1, teaspoon, baking powder > 1/2, teaspoon, baking soda > 1/2, teaspoon, salt > 1,, egg > 2, tablespoons, butter melted > ,, cooking spray > > | 3/4 | cup | milk | > | 2 | tablespoons | white vinegar | > | 1 | cup | all-purpose flour | > | 2 | tablespoons | white sugar | > | 1 | teaspoon| baking powder | > | 1/2 | teaspoon| baking soda | > | 1/2 | teaspoon| salt | > | 1 | | egg | > | 2 | tablespoons | butter melted | > | | | cooking spray | > > Scott > > > > > On Sun, Mar 12, 2017 at 5:26 PM, Vicente Vera > <mailto:vicente...@gmail.com>> wrote: > > > > Hello. In this case Org splits into columns everytime it sees a > > space, so "baking soda" ends up in two columns. A brute force > > solution: replace the spaces between words that shouldn't be put > > into separated columns with an underscore: > > > > 1_cup all-purpose_flour > > > > Convert it to an Org table and then do a quick M-x replace-string to > > replace '_' with ' '. > > > > 2017-03-12 15:14 GMT+00:00 Xebar Saram > <mailto:zelt...@gmail.com>>: > > > > Hi list > > > > so im trying to use orgmode to collect food recepies. i have one > > issue which is to convert text based ingridents list into org > > tables. > > > > for example take this list > > > > 3/4 cup milk > > 2 tablespoons white vinegar > > 1 cup all-purpose flour > > 2 tablespoons white sugar > > 1 teaspoon baking powder > > 1/2 teaspoon baking soda > > 1/2 teaspoon salt > > 1 egg > > 2 tablespoons butter, melted > > cooking spray > > > > if i mark this as a region and issue > > `org-table-create-or-convert-from-region` this is the result > > > > | 3/4 | cup | milk| | | > > | | | | > > | 2 | tablespoons | white | vinegar | (%or | better > > | yet | lemon | juice%) | > > | 1 | cup | all-purpose | flour | | > > | | | | > > | 2 | tablespoons | white | sugar | | > > | | | | > > | 1 | teaspoon| baking | powder | | > > | | | | > > | 1/2 | teaspoon| baking | soda| | > > | | | | > > | 1/2 | teaspoon| salt| | | > > | | | | > > | 1 | egg | | | | > > | | | | > > | 2 | tablespoons | butter, | melted | | > > | | | | > > | cooking | spray | | | | > > | | | | > > > > > > as you can see it got the amount (1/2) and the unit (cup) right > > yet the actual ingredients is cut into several columns > > > > i dont really know how to deal with this. is there a more > > intelligent way of auto directing the conversion to split it the > > correct way? > > > > if not any suggestions on how to convert it in a better way? > > perhaps a command to quick delete the separator (|) across all > > the column? > > > > thx alot in advance > > > > Z > > > > > > > >
[O] Git repository error
Hi. For a while i've been getting this error upon running 'make up0' from my local Org repository: fatal: read error: Connection reset by peer
Re: [O] exporting markdown with tables
There are several Markdown "forks" which have different sets of features. AFAIK the markdown exporter in Org is based upon John Gruber's Markdown, which does not include a syntax for tables. Thus all tables in Org documents get exported as HTML. A workaround is to wrap your Org tables as: #+BEGIN_EXPORT md | Name | Years | | Edward |44 | | Sylvia |45 | #+END_EXPORT On export to Markdown the tables will be kept unmodified as Org syntax. It is important that you know which flavor of Markdown you're targeting, because not all versions accept tables in Org syntax. Pandoc's Markdown have a similar syntax for "pipe tables". However, you may type all tables in any syntax accepted by your Markdown version and keep them wrapped in #+BEGIN_EXPORT tags. 2017-06-03 13:41 GMT+00:00 Peter Davis : > > I'd like to be able to move easily between org-mode and the IOS app > Editorial, which is mainly based around markdown syntax. I can > easily export markdown from org-mode, but the tables seems to come through as > straight HTML, as opposed to markdown's table > syntax. This makes it more difficult to edit the resulting files. > > Is there a way to get org to export to markdown using md's table syntax? > > (FWIW, I tried using pandoc, but this just removed the table syntax > altogether, so an entire table would just run together into a > paragraph of gibberish.) > > Thanks, > -pd > >
Re: [O] exporting markdown with tables
Cool, you're welcome. It is not the most convenient solution, but keeping your tables in Editorial Markdown syntax should work: #+BEGIN_EXPORT md Cat | Fur | --- | --- | A | A lot | B | None | #+END_EXPORT 2017-06-03 16:46 GMT+00:00 Peter Davis : > Thanks, Vincente. > > I'm specifically aiming at the Markdown syntax supported by the Editorial > app, which does include markup for tables. Unfortunately, it looks like > Editorial's Markdown doesn't use the initial '|', so simply exporting the > org markup won't work without some editing. > > Thanks! > -pd > > On Sat, Jun 3, 2017, at 12:31 PM, Vicente Vera wrote: >> There are several Markdown "forks" which have different sets of features. >> >> AFAIK the markdown exporter in Org is based upon John Gruber's >> Markdown, which does not include a syntax for tables. Thus all tables >> in Org documents get exported as HTML. >> >> A workaround is to wrap your Org tables as: >> >> #+BEGIN_EXPORT md >> | Name | Years | >> | Edward |44 | >> | Sylvia |45 | >> #+END_EXPORT >> >> On export to Markdown the tables will be kept unmodified as Org syntax. >> >> It is important that you know which flavor of Markdown you're >> targeting, because not all versions accept tables in Org syntax. >> Pandoc's Markdown have a similar syntax for "pipe tables". However, >> you may type all tables in any syntax accepted by your Markdown >> version and keep them wrapped in #+BEGIN_EXPORT tags. >> >> 2017-06-03 13:41 GMT+00:00 Peter Davis : >> > >> > I'd like to be able to move easily between org-mode and the IOS app >> > Editorial, which is mainly based around markdown syntax. I can >> > easily export markdown from org-mode, but the tables seems to come >> > through as straight HTML, as opposed to markdown's table >> > syntax. This makes it more difficult to edit the resulting files. >> > >> > Is there a way to get org to export to markdown using md's table syntax? >> > >> > (FWIW, I tried using pandoc, but this just removed the table syntax >> > altogether, so an entire table would just run together into a >> > paragraph of gibberish.) >> > >> > Thanks, >> > -pd >> > >> > > > > -- > Peter Davis > www.techcurmudgeon.com >
[O] "Minimal" LaTeX export
Hello
I'm trying to export a simple document to a LaTeX buffer, but just the
main content, without a preamble nor the "document" environment. The
main objective is to export several Org documents which are parts of a
larger LaTeX report. These parts are then included by means of the
"input" command.
This is what I came up with, but, of course, there are other functions
involved that seem too expensive to modify:
(defun this-is-just-a-test ()
(interactive)
(require 'ox-latex)
(let ((org-export-with-date nil)
(org-export-with-toc nil)
(org-latex-classes
(append org-latex-classes
'(("nothing-at-all"
"[NO-DEFAULT-PACKAGES]
[NO-PACKAGES]
[NO-EXTRA]"
;; "book"
("\\part{%s}" . "\\part*{%s}")
("\\chapter{%s}" . "\\chapter*{%s}")
("\\section{%s}" . "\\section*{%s}")
("\\subsection{%s}" . "\\subsection*{%s}")
("\\subsubsection{%s}" . "\\subsubsection*{%s}")
(org-latex-default-class "nothing-at-all")
(org-latex-with-hyperref nil)
(org-latex-hyperref-template nil)
(org-latex-prefer-user-labels t))
(org-latex-export-as-latex)))
Is there a "clean", elispy way to do this?
Re: [O] "Minimal" LaTeX export
That is amazing. Thank you very much!
Yes, that's a good idea (include files); will look into it.
El dic 16, 2017 2:46 PM, "Berry, Charles" escribió:
> On Dec 16, 2017, at 8:48 AM, Vicente Vera wrote:
>
> I'm trying to export a simple document to a LaTeX buffer, but just the
> main content, without a preamble nor the "document" environment.
You want `(org-latex-export-as-latex nil nil nil t)' or `C-c C-e C-b l L'.
,[ C-h f org-latex-export-as-latex RET ]
| org-latex-export-as-latex is an interactive autoloaded compiled Lisp
| function in ‘ox-latex.el’.
|
| (org-latex-export-as-latex &optional ASYNC SUBTREEP VISIBLE-ONLY
| BODY-ONLY EXT-PLIST)
|
| Export current buffer as a LaTeX buffer.
|
| [...]
|
| When optional argument BODY-ONLY is non-nil, only write code
| between "\begin{document}" and "\end{document}".
|
| [...]
`
> The main objective is to export several Org documents which are parts of a
> larger LaTeX report. These parts are then included by means of the
> "input" command.
Why not use include keywords in the org document? They can, if needed,
refer to sections in the parent document.
See (info "(org) Include files")
HTH,
Chuck
[O] Make org-fill-paragraph behave as Emacs 26.1 fill-paragraph
Hi. Since Emacs 26.1 ‘fill-paragraph’ doesn't change the buffer contents if no filling is needed on the current paragraph. It would be nice if ‘org-fill-paragraph’ worked the same way. Not a very relevant change to make, really, but still. Just to avoid those pesky false-positive asteriks!
Re: [O] Make org-fill-paragraph behave as Emacs 26.1 fill-paragraph
Nice, thanks. The 'next' branch will be merged with 'master' for Org 9.2 release? El jue, jun 14, 2018 16:07, Nicolas Goaziou escribió: > Hello, > > Vicente Vera writes: > > > Since Emacs 26.1 ‘fill-paragraph’ doesn't change the buffer contents > > if no filling is needed on the current paragraph. It would be nice if > > ‘org-fill-paragraph’ worked the same way. > > > > Not a very relevant change to make, really, but still. Just to avoid > > those pesky false-positive asteriks! > > Implemented in "next" branch. Thank you. > > Regards, > > -- > Nicolas Goaziou >
