emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jordi Inglada <jordi.inglada@cesbio.cnes.fr>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Title page for book latex export
Date: Tue, 19 Oct 2010 16:36:04 +0200	[thread overview]
Message-ID: <19645.44244.603501.187098@goeland.ups-tlse.fr> (raw)
In-Reply-To: <493995.8239.1287496847211.JavaMail.root@zm-cesbio-01>


No problem. And thanks again for your help.

Jordi


Nick Dokos writes:
 > Jordi Inglada <jordi.inglada@cesbio.cnes.fr> wrote:
 > 
 > 
 > > Nick Dokos writes: 
 > >  > <rant>
 > >  > ...
 > >  > </rant>
 > >  > 
 > > 
 > > Sorry. I did not notice that my not understanding what the problem was
 > > was going to upset anybody. I'll be more careful next time.
 > > 
 > 
 > A couple of points:
 > 
 >     o although I meant what I said in the <rant> seriously, I was not
 >       upset. I guess my humor is dry as dust, but I can assure you I
 >       was chuckling while composing the mail.
 > 
 >     o I *certainly* was not upset at your not understanding the problem.
 >       This is exactly what the list is about. And your question was
 >       entirely appropriate for the list.
 > 
 >     o Although your post was the trigger, the rant was not meant for you
 >       personally: it was meant for the whole list. It is often the case
 >       that people describe a problem with very little detail and it
 >       takes a series of back-and-forths before we can really understand
 >       what the problem is. Sometimes that's inevitable but many times
 >       it can be avoided. My suggestion was to include enough detail
 >       in the original report so the back-and-forth can be avoided to
 >       the extent possible.
 > 
 > So I hope I did not offend you and if I did offend you, I apologize:
 > that was not my purpose at all, and a rant that offends but does not
 > educate is no good at all.
 > 
 > Nick
 > 
 > 

      parent reply	other threads:[~2010-10-19 14:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-18  9:39 Title page for book latex export Jordi Inglada
2010-10-18 17:44 ` Jeff Horn
     [not found] ` <9312871.193.1287423634931.JavaMail.root@zm-cesbio-01>
2010-10-18 20:19   ` Jordi Inglada
2010-10-18 21:43     ` Nick Dokos
2010-10-19  6:18       ` Carsten Dominik
     [not found]     ` <28722569.197.1287437982941.JavaMail.root@zm-cesbio-01>
2010-10-19  6:13       ` Jordi Inglada
2010-10-19 14:04         ` Nick Dokos
2010-10-20  2:33           ` Jeff Horn
2010-10-20  4:11             ` Nick Dokos
     [not found]               ` <AANLkTiks0Om7sdkFfiR5CiJncixhD5AKE2htZcexKLcW@mail.gmail.com>
2010-10-20  4:49                 ` Jeff Horn
2010-10-20  5:05               ` Jambunathan K
2010-10-27 22:28               ` Bastien
2010-10-28  9:00                 ` Jeff Horn
     [not found]         ` <493995.8239.1287496847211.JavaMail.root@zm-cesbio-01>
2010-10-19 14:36           ` Jordi Inglada [this message]

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=19645.44244.603501.187098@goeland.ups-tlse.fr \
    --to=jordi.inglada@cesbio.cnes.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.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).