edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev]      wordexp again
Date: Sat, 18 Apr 2015 07:34:35 -0400	[thread overview]
Message-ID: <20150318073435.eklhad@comcast.net> (raw)
In-Reply-To: <20150418104919.GI5949@toaster.adamthompson.me.uk>

> What the last couple of days have shown is that making undiscussed changes is
> just going to get circular due to differing user requirements and opinions.

Yes and we all did that, when initially my intent was just to fix a bug.
But instead we changed the user interface, things expanded when they didn't before,
and conversely, changing the meaning of ` etc,
and some of the edbrowse users, who are not on this list
contacted me and were confused.
So now it works all as it did before, except the bug is fixed,
and the code is much cleaner inside.
Of course there's nothing wrong with cleaning up code,
but we do have to talk more and plan more
before changing the user interface.

I had the same problem with some of the plugin work,
which we all agreed was great, and even the users agreed was great, so no trouble there,
they are really quite enthusiastic about it,
but we rather innocently said,

Hey let's change mime { to plugin { in .ebrc

Sure that makes sense, but some of my users out there had edbrowse fail on startup
for reasons they didn't understand.
And even if they waited til the next release, it would have been the same problem.
No backward compatibility.
So at their suggestion I allow either syntax now
mime { or plugin {
and edbrowse runs again with the previous .ebrc

I have to temper what I do, and what we do, with some feedback that I get
from others that is, unfortunately, not always on this list.
It is, I suppose, my job to relay some of this information to this list,
so we can all talk about it.
Sorry if I missed some of these steps.

Karl Dahlke

  reply	other threads:[~2015-04-18 11:35 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-16 21:40 Karl Dahlke
2015-04-17  7:12 ` Adam Thompson
2015-04-17 12:50   ` Adam Thompson
2015-04-17 13:33     ` Karl Dahlke
2015-04-17 17:59       ` Adam Thompson
2015-04-17 13:47     ` Karl Dahlke
2015-04-17 18:01     ` Karl Dahlke
2015-04-17 21:34       ` Adam Thompson
2015-04-17 21:58         ` Adam Thompson
2015-04-17 22:25           ` Karl Dahlke
2015-04-17 22:43             ` Adam Thompson
2015-04-17 23:14               ` Karl Dahlke
2015-04-17 22:28           ` Adam Thompson
2015-04-17 22:39             ` Karl Dahlke
2015-04-18 10:53               ` Adam Thompson
2015-04-18  4:18     ` Karl Dahlke
2015-04-18 10:49       ` Adam Thompson
2015-04-18 11:34         ` Karl Dahlke [this message]
2015-04-18 13:09           ` Adam Thompson
2015-04-18 19:33             ` Chris Brannon
2015-04-18 20:05               ` Adam Thompson
2015-04-18 23:03                 ` Chris Brannon
2015-04-18 12:36         ` Karl Dahlke
2015-04-18 12:54           ` Adam Thompson
2015-04-18 13:09             ` Karl Dahlke
2015-04-18 13:24               ` Adam Thompson
2015-04-18 13:45                 ` Karl Dahlke
2015-04-18 17:44                   ` Adam Thompson
2015-04-18 19:48                     ` Karl Dahlke
  -- strict thread matches above, loose matches on Subject: below --
2015-01-09 22:44 Karl Dahlke
2015-01-09 22:19 Karl Dahlke
2015-01-09 22:29 ` Chris Brannon
2015-01-09 21:16 Chris Brannon

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150318073435.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.the-brannons.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.
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 NNTP newsgroup(s).