From: Jeff Horn <jrhorn424@gmail.com>
To: nicholas.dokos@hp.com
Cc: Org-mode ml <emacs-orgmode@gnu.org>
Subject: Re: Title page for book latex export
Date: Wed, 20 Oct 2010 00:49:42 -0400 [thread overview]
Message-ID: <AANLkTinS9mhAiFTrRV3pDrr9uyASaJemPpMh5uNJ=qHo@mail.gmail.com> (raw)
In-Reply-To: <AANLkTiks0Om7sdkFfiR5CiJncixhD5AKE2htZcexKLcW@mail.gmail.com>
Responded to Nick instead of CC'ing the group, as I am wont to do.
Apologies. My e-mail is below.
>> There is a fairly clear list of expectations in section 1.4, Feedback,
>> of the Org manual. And the "How to contribute" page on Worg
>> (http://orgmode.org/worg/org-contribute.php) contains the admonition:
>
> I fully admit to having read those before. I probably internalized
> most of what was mentioned there, which is not to say I ask good
> questions, only that my first reaction was to look first at
> http://orgmode.org/index.html#sec-5_2 for an admonition, and secondly
> to look at http://orgmode.org/worg/org-faq.php. The mailing list
> section at this second link contains no admonition.
>
> These just seem like natural places to me to place a section on
> (n)etiquette. But I obviously found the others, since I do recall
> reading them at some point.
>
>> Perhaps people asking questions don't think of them as bug reports, but
>> they are: if one cannot find a way to do something, it's a bug: it may
>> be a code bug or a documentation bug - or it may be a user bug. But to
>> figure out which it is, we need information: relevant information to be
>> sure, but complete information as well - as complete as possible.
>
> I had never taken that perspective. Good point.
>
>> See the thread starting at
>>
>> http://thread.gmane.org/gmane.emacs.orgmode/16970
>
> Thanks also for this. Good read.
>
> Best wishes,
> Jeff
>
> --
> Jeffrey Horn
> Graduate Lecturer and PhD Student in Economics
> George Mason University
>
> (704) 271-4797
> jhorn@gmu.edu
> jrhorn424@gmail.com
>
> http://www.failuretorefrain.com/jeff/
next prev parent reply other threads:[~2010-10-20 4:50 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 [this message]
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
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='AANLkTinS9mhAiFTrRV3pDrr9uyASaJemPpMh5uNJ=qHo@mail.gmail.com' \
--to=jrhorn424@gmail.com \
--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).