emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: windy <chxp_moon@163.com>
Cc: Holger Wenzel <drholgerwenzel@gmail.com>,
	emacs-orgmode <emacs-orgmode@gnu.org>,
	John Kitchin <jkitchin@andrew.cmu.edu>
Subject: Re: Organizing and taming hectic Academia work (faculty viewpoint)? Tips or a good guides sought after :)
Date: Wed, 10 Jun 2015 19:51:23 +0100	[thread overview]
Message-ID: <87oaknz9as.fsf@ucl.ac.uk> (raw)
In-Reply-To: <7e093509.51e.14ddb300091.Coremail.chxp_moon@163.com> (windy's message of "Wed, 10 Jun 2015 09:57:45 +0800 (CST)")

On Wednesday, 10 Jun 2015 at 09:57, windy wrote:
> Another question, I am a student , I think it is a big problem that
> how to exchange you article with your teacher, because the teacher
> will comment or revise your article once again and again.
>
> However, Many teachers will not use emacs to write articles and also
> the pdf file is not so convenient to do some modification, how will
> you deal with the problem ?

As John has already said, go with the flow and use whatever system your
teacher prefers...

The students in my group quickly learn that they get more useful
feedback from me if they give me LaTeX or org files instead of Word!
It's not because I wish to penalise them, of course.  It's that I don't
have Word so I get them to give me PDF to ensure the maths come through
properly (libreoffice is not particularly good when it comes to
mathematics).  I only end up commenting indirectly on any document they
give me.  On the other hand, if they give me LaTeX or org, I comment
directly within their documents and/or suggest changes when appropriate.

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.1, Org release_8.3beta-1147-g0e5069.dirty

  parent reply	other threads:[~2015-06-10 18:51 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-08 16:39 Organizing and taming hectic Academia work (faculty viewpoint)? Tips or a good guides sought after :) Xebar Saram
2015-06-08 21:16 ` M
2015-06-09  5:13   ` Xebar Saram
2015-06-09  7:00     ` Holger Wenzel
2015-06-09 13:21       ` John Kitchin
2015-06-10  1:57         ` windy
2015-06-10 13:49           ` John Kitchin
2015-06-10 14:14             ` Ken Mankoff
2015-06-10 20:58               ` Titus von der Malsburg
2015-06-11  5:30                 ` Rasmus
2015-06-11 14:56                 ` Phillip Lord
2015-06-11 17:02                   ` John Kitchin
2015-06-12 13:24                     ` Phillip Lord
2015-06-10 14:16             ` Julian Burgos
2015-06-11  2:07               ` windy
2015-06-11  5:38                 ` Rasmus
2015-06-11 12:19                   ` windy
2015-06-11 12:18                 ` Ken Mankoff
2015-06-11 12:54                   ` windy
2015-06-12 14:02               ` Ken Mankoff
2015-06-13 19:06                 ` Xebar Saram
2015-06-13 19:52                   ` John Kitchin
2015-06-15 17:33                 ` Julian Burgos
2015-06-16  1:49               ` Bob Newell
2015-06-16 23:15                 ` Alan L Tyree
2015-06-10 18:51           ` Eric S Fraga [this message]
2015-06-09  9:49 ` Alan Schmitt
2015-08-26 14:17 ` Anders Johansson

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=87oaknz9as.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=chxp_moon@163.com \
    --cc=drholgerwenzel@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jkitchin@andrew.cmu.edu \
    /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).