emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Detlef Steuer <detlef.steuer@gmx.de>
To: emacs-orgmode@gnu.org
Subject: Re: missing autoloads / (void-variable org-version)
Date: Thu, 26 Apr 2012 13:55:09 +0200	[thread overview]
Message-ID: <20120426135509.453fe598@vknecht-intel.unibw-hamburg.de> (raw)
In-Reply-To: 87vcknm43o.fsf@Rainer.invalid

> Since my Makefile branch was merged I've been getting flak for breaking
> certain setups.  Now, the change didn't actually break them, but I did
> make (perhaps foolishly) a deliberate decision to make that particular
> breakage fatal rather than silent.  It would be very easy to continue to
> paper over the breakage and pretend things are working when they're not.
> What irritates me greatly is that quite a few of the people that insist
> on this "solution" are the ones who would have to deal with the
> Heisenbugs thus introduced.  So let me explain once more what is broken:

Hmm. I was biten by the makefile change but hopefully my report didn't
count as "flak". 

I have absolutely no problem with any reasonable change in the makefile.
But your description of the situation before and after the makefile
change is not entirely correct.  
Before: May be I had a broken setup and didn't know. Nevertheless it
After: May be conceptually your new makefile improved the build
process. But now my setup was broken. ;-)

And here comes the moment when you just wanted to do some routine work,
namely publish some notes for the upcoming lecture, normally a one
minute job, well set-up and tested. And all you get is some error. Time
is ticking away, next org-mode scheduled APPT in 5 min. We all know

My guess: It was too easy to miss that action was required on a user's
side. May be a hint that make targets changed and that under some
circumstances make update could fail and a hint with some exclamation
marks that batch exporting now requires --load org-install.el and not
only --load org.el would have reduced mail traffic a lot. If there was
such a note at least I missed it. 

Definitely keep up your work and improve the build process! I'm happy
to change my scripts if I know I need to and better still if I
understand why I should!  (Thx for your explanation!)


  parent reply	other threads:[~2012-04-26 11:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26  5:52 missing autoloads / (void-variable org-version) Achim Gratz
2012-04-26 10:23 ` Sebastien Vauban
2012-04-26 16:06   ` Achim Gratz
2012-04-26 19:30     ` Sebastien Vauban
2012-04-26 22:03       ` Bastien
2012-04-26 22:04       ` Bastien
2012-04-26 11:55 ` Detlef Steuer [this message]
2012-04-26 12:01 ` Martyn Jago
2012-04-26 16:14   ` Achim Gratz
2012-04-26 13:15 ` Bastien
2012-04-26 19:03   ` Achim Gratz
2012-04-26 21:54     ` Bastien
2012-04-29  9:53       ` Michael Sperber
2012-04-29 18:57         ` Achim Gratz

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:

  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=20120426135509.453fe598@vknecht-intel.unibw-hamburg.de \
    --to=detlef.steuer@gmx.de \
    --cc=emacs-orgmode@gnu.org \


* 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


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).