From: Karl Dahlke <email@example.com>
Subject: [edbrowse-dev] redundent
Date: Tue, 24 Apr 2018 09:03:38 -0400 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 698 bytes --]
A good programmer is always annoyed by redundent work.
combine the code into one routine and call it from different places, possibly with different parameters.
But I didn't really notice this one until my translating friends pointed it out to me.
We have some sample ebrc config files in the doc directory, which are installed in /usr/share/doc/edbrowse, and referenced from the users guide,
then, we have sample ebrc files that are created if you bring up edbrowse and have no config file in your home directory.
These are similar but not identical.
My translating friends say, "I just did this, and now I'm translating almost the same thing again?"
What should we do here?
reply other threads:[~2018-04-24 13:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).