Re: [O] "Minimal" LaTeX export

[Vicente Vera]

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

Re: [O] Can export the files with bibliography only to LaTeX

[Adonay Felipe Nogueira]

This serves as good argumentation:

For all of those reading this and which have other people making demands
such as "you must use this (non-free) software", please remind these
people that what matters is the content, not the tool in this case.

Besides, if they really want to go the "efficiency" route, they should
just accept plain text files since these are lightweight. ;)

2017-12-16T08:43:06+1100 Tim Cross wrote:
> The saddest part of this message is the last line about your publishers
> also requiring word doc! A long time since I had to deal with
> publishers, but at least they use to require Latex (albeit often with
> weird *.sty files!).
>
> After 17 years working in an 'admin' area of a University, I got to the
> end of my tether and resigned 3 weeks ago. A big part of this was due to
> the extent the administrative arm is now dictating direction and a
> feeling the tail is now wagging the dog. Too much of what is being
> required is based on making the administration 'efficient' rather than
> focusing on making teaching, learning and research effective.
>
> Good news is 7 days after finishing, I got a new position within a
> research centre where my role is 100% technical, I'm free to use
> whatever 'tool' I want provided I produce the final outcome i.e. good
> looking presentations and documents (all org and Latex!) and solid
> technical solutions.
>
> Like others who have replied, Pandoc was my 'goto' solution for dealing
> with administration. It is an incredibly powerful tool and worth some
> time investment IMO.
>
> Tim

Re: [O] "Minimal" LaTeX export

[Berry, Charles]

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

Re: [O] "Minimal" LaTeX export

[Rasmus]

Hi,

Would the body only export option in the export dispatcher work? (C-c C-e
and then C-b)?

Rasmus

-- 
C is for Cookie

[O] "Minimal" LaTeX export

[Vicente Vera]

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] Git repository error

[Kaushal Modi]

I clone worg on repo.or.cz and that started failing too.

=
Project: worg

Mirroring from URL "git://orgmode.org/worg.git"

Fetching origin
fatal: read error: Connection reset by peer
error: Could not fetch origin
=


On Sat, Dec 16, 2017, 4:45 AM Detlef Steuer  wrote:

> Am Thu, 14 Dec 2017 10:40:09 -0500
> schrieb Josiah Schwab :
>
> > Hello,
> >
> > For about the past day, I've been getting this error upon running
> > 'make update' from my local Org repository:
> >
> >   fatal: read error: Connection reset by peer
> >   error: Could not fetch origin
>
> I can confirm this issue at least since 13th of December.
>
> Greetings
> Detlef
>
>
> >
> > If I recall correctly, this has happened before and the resolution was
> > that some admin needed to do something server-side.
> >
> > Thanks,
> > Josiah
> >
> >
>
>
>
>
> --

Kaushal Modi

[O] Org table: how to reference part of the rows

[Qiang Fang]

The last column is the ratio between column b and a, the last row is the
sum of
each row, the second formula only applies from the second row to the row
before
last row. The table that doesn't work is:

| |  a | b |  ratio |
| |  0.797 | 0.780 ||
| |  0.744 | 0.730 ||
| | 12.707 | 2.384 ||
| sum | 14.248 | 3.114 | 0.92040988 |
| ^   |  x | y ||
#+tblfm: $x=vsum(@2..@-1) :: $y=vsum(@3..@-1)
#+tblfm: $4 = ($3 / $2) * 100

Re: [O] Emacs sagmentation fault error on a big org-mode file movement

[Neil Jerram]

I would suggest (but without detailed knowledge of current emacs practice):

1. Report your exact emacs version.

2. Install a corresponding debug symbols package, if your distro 
provides that.  That should add a lot more interesting detail to the 
backtrace.


3. To go further, repro under GDB, ideally with corresponding source 
code.  Then you could explore the immediate cause of the segfault.


    Neil


On 16/12/17 04:27, numbch...@gmail.com wrote:
I have a big org-mode file which is overview at startup. When I 
navigate around with [C-v] and [M-v]. The Emacs crashed.


Here is the output from command-line:
```
Fatal error 11: Segmentation fault
Backtrace:
emacs[0x51195e]
emacs[0x4f739a]
emacs[0x50fe3e]
emacs[0x510058]
emacs[0x5100dc]
/usr/lib/libpthread.so.0(+0x11da0)[0x7fcb1cdcada0]
emacs[0x4caa74]
emacs[0x45b2b5]
emacs[0x4613e9]
emacs[0x41eb42]
emacs[0x42087c]
emacs[0x42157a]
emacs[0x421567]
emacs[0x421567]
emacs[0x42351d]
emacs[0x458015]
emacs[0x501893]
emacs[0x50465a]
emacs[0x5061dc]
emacs[0x56c85e]
emacs[0x4f7754]
emacs[0x56c7cd]
emacs[0x4f76eb]
emacs[0x4fc313]
emacs[0x4fc636]
emacs[0x41b302]
/usr/lib/libc.so.6(__libc_start_main+0xea)[0x7fcb1bf30f4a]
emacs[0x41c01a]
[1]    17259 segmentation fault (core dumped)  emacs --debug-init
```
Is there a way to debug this?
I know it is not possible to invoke edebug on anything internal Emacs.
So is there any system (Linux)  solution?
Like system process dump or traceback.

I'm using latest version `master` branch source code Org-mode.
Emacs is from compiled `master` branch  source code too.

[stardiviner]     GPG key ID: 47C32433
IRC(freeenode): stardiviner Twitter:  @numbchild
Key fingerprint = 9BAA 92BC CDDD B9EF 3B36  CB99 B8C4 B8E5 47C3 2433
Blog: http://stardiviner.github.io/

Re: [O] Emacs sagmentation fault error on a big org-mode file movement

[numbch...@gmail.com]

That's very helpful . Thanks very much.

[stardiviner] GPG key ID: 47C32433
IRC(freeenode): stardiviner Twitter:  @numbchild
Key fingerprint = 9BAA 92BC CDDD B9EF 3B36  CB99 B8C4 B8E5 47C3 2433
Blog: http://stardiviner.github.io/

On Sat, Dec 16, 2017 at 4:38 PM, Eli Zaretskii  wrote:

> > From: "numbch...@gmail.com" 
> > Date: Sat, 16 Dec 2017 12:27:58 +0800
> >
> > Is there a way to debug this?
>
> Run Emacs under a debugger, trigger the crash, and produce a more
> helpful backtrace by typing the "bt" command at GDB prompt.
>
> Please report all of that to the Emacs issue tracker using the command
> report-emacs-bug.  If you can attach the file which causes the crash,
> please do.  Further discussion of this should be on the bug list, not
> here (many Emacs developers don't read this list).
>
> Thanks.
>

Re: [O] Git repository error

[Detlef Steuer]

Am Thu, 14 Dec 2017 10:40:09 -0500
schrieb Josiah Schwab :

> Hello,
> 
> For about the past day, I've been getting this error upon running
> 'make update' from my local Org repository:
> 
>   fatal: read error: Connection reset by peer
>   error: Could not fetch origin

I can confirm this issue at least since 13th of December.

Greetings
Detlef


> 
> If I recall correctly, this has happened before and the resolution was
> that some admin needed to do something server-side.
> 
> Thanks,
> Josiah
> 
> 

Re: [O] Emacs sagmentation fault error on a big org-mode file movement

[Eli Zaretskii]

> From: "numbch...@gmail.com" 
> Date: Sat, 16 Dec 2017 12:27:58 +0800
> 
> Is there a way to debug this?

Run Emacs under a debugger, trigger the crash, and produce a more
helpful backtrace by typing the "bt" command at GDB prompt.

Please report all of that to the Emacs issue tracker using the command
report-emacs-bug.  If you can attach the file which causes the crash,
please do.  Further discussion of this should be on the bug list, not
here (many Emacs developers don't read this list).

Thanks.