emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Problem exporting code
Date: Wed, 23 Jan 2013 08:27:43 +0100	[thread overview]
Message-ID: <87pq0wfjf4.fsf@Rainer.invalid> (raw)
In-Reply-To: m1a9s16m97.fsf@tsdye.com

Thomas S. Dye writes:
> I think you and I have different definitions of "problem". From my
> user's perspective, something I "get away with," i.e., that doesn't have
> an effect on my work and productivity, isn't a problem.

That may well be true.  I'm firmly in the "fail fast and crash loudly"
camp.  In other words, if there is a problem, it should make itself
known at the earliest possible moment in a way that makes clear that it
needs to be fixed ASAP.  I encounter many folks that disagree with that
position, but usually only until one of those problems that fail to
clearly announce themselves causes them to lose important work later on.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

  reply	other threads:[~2013-01-23  7:28 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-20 23:44 Problem exporting code Ken Williams
2013-01-21  0:31 ` Ken Williams
2013-01-21  3:15   ` Eric S Fraga
2013-01-21  4:57     ` Ken Williams
2013-01-21  5:36       ` John Hendy
2013-01-21  5:38         ` John Hendy
2013-01-21  6:05         ` Ken Williams
2013-01-21  7:39           ` Eric S Fraga
2013-01-21 15:58             ` Ken Williams
2013-01-21 16:48               ` John Hendy
2013-01-21 17:45                 ` Ken Williams
2013-01-21 22:16                   ` John Hendy
2013-01-21 22:51                     ` Ken Williams
2013-01-22  0:14                       ` Thomas S. Dye
     [not found]                       ` <CA+M2ft_nyHsjC3V0FPvL+NbYBTP1FGKLqF0=miX09uByhS_oKA@mail.gmail.com>
2013-01-22  2:48                         ` Ken Williams
2013-01-22  7:01                           ` Thomas S. Dye
2013-01-22  7:49                             ` Bastien
2013-01-22 11:13                               ` Thorsten Jolitz
2013-01-22 11:54                                 ` Bastien
2013-01-22 12:58                                   ` Thorsten Jolitz
2013-01-22 19:45                                   ` Thorsten Jolitz
2013-01-22 21:41                                     ` Bastien
2013-01-22 13:02                               ` Ken Williams
2013-01-22 13:10                                 ` Bastien
2013-01-22 17:44                               ` Achim Gratz
2013-01-22 21:41                                 ` Bastien
2013-01-22 17:37                             ` Achim Gratz
2013-01-22 19:39                               ` Thomas S. Dye
2013-01-23  7:27                                 ` Achim Gratz [this message]
2013-01-21 23:43               ` Eric S Fraga
2013-01-21  6:11         ` Ken Williams
2013-01-21  5:52       ` Ken Williams

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=87pq0wfjf4.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \
    /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).