emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <ucecesf@ucl.ac.uk>
To: Torsten Wagner <torsten.wagner@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Writing a dissertation using org-mode
Date: Fri, 05 Mar 2010 09:00:14 +0000	[thread overview]
Message-ID: <878wa7m9cx.wl%ucecesf@ucl.ac.uk> (raw)
In-Reply-To: <4B8F462D.1090702@gmail.com>

On Thu, 04 Mar 2010 14:33:33 +0900, Torsten Wagner <torsten.wagner@gmail.com> wrote:
> On 03/04/2010 01:45 PM, Henri-Paul Indiogine wrote:
> > I started writing my doctoral dissertation in history using org-mode. I
> > am also using git.el for my version control and gnus for my email. Of
> > course I export my org file to LaTeX which I compile to pdf.  My
> > bibliography is managed using BibTeX.
> 
> please consider that you might have to follow a very stricy layout
> style depening on your university, department, lab or supervisor. If

[...]

> I'm not sure how good org-mode might be usable in that case. org-mode
> is really great and I try to use it for many purposes. However, for a
> thesis I would use directly LaTeX which gives me a bit more control of
> what is going on.

Torsten,

if I may (respectfully) disagree?  Having examined too many PhD theses
to count, I would prefer PhD candidates spent more of their time
worrying about the content and organisation of their thesis than the
actual layout.  Unlike the preparation of camera ready copy for
conferences, say, most of the defaults taken by LaTeX are usually fine
once you've set up the layout to meet the university's requirements
(which are usually only about page size, margins and font sizes).  The
great thing about using org-mode for writing is the outlining and the
ability to easily move sections around.

Being able to insert LaTeX code directly when required means that
there is seldom the need to edit the actual LaTeX code generated by
org-mode (bugs excepted, of course, but not only are these few and far
between but Carsten et al. usually fix bugs very quickly).

cheers,
eric

  parent reply	other threads:[~2010-03-05  9:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04  4:45 Writing a dissertation using org-mode Henri-Paul Indiogine
2010-03-04  5:33 ` Torsten Wagner
2010-03-04  9:51   ` Scot Becker
2010-03-04 17:12   ` Henri-Paul Indiogine
2010-03-05  8:58     ` Detlef Steuer
2010-03-05  9:00   ` Eric S Fraga [this message]
2010-03-05 10:14     ` Sven Bretfeld
2010-03-05 17:41       ` Markus Heller
2010-03-06 23:54         ` Eric S Fraga
2010-03-07  3:10           ` Thomas S. Dye
2010-03-09 15:16             ` Eric S Fraga
2010-03-09 16:27             ` Carsten Dominik
2010-03-21 19:19               ` Thomas S. Dye
2010-03-22  8:49                 ` Carsten Dominik
2010-03-04 14:02 ` Maurizio Vitale
2010-03-04 17:33   ` Thomas S. Dye
2010-03-04 18:40     ` Henri-Paul Indiogine

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878wa7m9cx.wl%ucecesf@ucl.ac.uk \
    --to=ucecesf@ucl.ac.uk \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=torsten.wagner@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).