On Mon, 2011-02-07 at 08:38 -0500, Matthew Barnes wrote:
> On Sun, 2011-02-06 at 16:10 -0800, les wrote:
> > As you gain experience, you too, will come to agree with these comments.
> > I can remember writing the kind of comments you wrote here. I suggest
> > that you frame this entire mail and ha
On Sun, 2011-02-06 at 16:10 -0800, les wrote:
> As you gain experience, you too, will come to agree with these comments.
> I can remember writing the kind of comments you wrote here. I suggest
> that you frame this entire mail and hang it over your desk. If I am
> still around in 10 years, send m
On Sun, 2011-02-06 at 15:48 -0800, les wrote:
> On Thu, 2011-02-03 at 22:02 -0430, Patrick O'Callaghan wrote:
> > On Thu, 2011-02-03 at 15:04 -0800, les wrote:
> > > With that said, here is a snippet from the gconf stuff for evolution:
> > >
> > > Directly from the file:
> > >
On Sun, 2011-02-06 at 16:10 -0800, les wrote:
> > If in fact you "write converters between systems" then you should *LOVE*
> > g-conf; it's XML! Meaning you can reliably, easily, and quickly process
> > the contents. Verses the crap-hole that is a "text file".
> A text file can indeed be a crap
>
> As you gain experience, you too, will come to agree with these comments.
> I can remember writing the kind of comments you wrote here. I suggest
> that you frame this entire mail and hang it over your desk. If I am
> still around in 10 years, send me a note about this then.
I have no idea
I see your years of experience have not taught you how to trim posts ...
> >
> XML means eXtended Meta Language.
No it doesn't. It stands for eXtensible Markup Language.
> It is a programming language with
> structure and meaning, and it is extensible. You can call it a data
> descriptio
On Fri, 2011-02-04 at 06:13 -0500, Adam Tauno Williams wrote:
> On Fri, 2011-02-04 at 09:30 +, Pete Biggs wrote:
> > > How many of you can read and understand this bit of code?
> > My gconfd can and that's all that matters. They are NOT text config
> > files like /etc/yum.conf.
> > > I especi
On Fri, 2011-02-04 at 09:30 +, Pete Biggs wrote:
> > HTML code is bad to begin with due to its fundamental formatting, but
> > leaving out linefeeds, tabs, and spaces just makes it worse. Would you
> > like reading a book with no punctuation, no paragraphs, and lack of
> > structure? Yet
On Thu, 2011-02-03 at 22:02 -0430, Patrick O'Callaghan wrote:
> On Thu, 2011-02-03 at 15:04 -0800, les wrote:
> > With that said, here is a snippet from the gconf stuff for evolution:
> >
> > Directly from the file:
> > --
On Fri, 2011-02-04 at 09:30 +, Pete Biggs wrote:
> > How many of you can read and understand this bit of code?
> My gconfd can and that's all that matters. They are NOT text config
> files like /etc/yum.conf.
> > I especially dislike the ##.#.#@localhost.localdomain
> > filename.
> HTML code is bad to begin with due to its fundamental formatting, but
> leaving out linefeeds, tabs, and spaces just makes it worse. Would you
> like reading a book with no punctuation, no paragraphs, and lack of
> structure? Yet I see lots of that kind of documentation, and even more
>
On Thu, 2011-02-03 at 15:04 -0800, les wrote:
> With that said, here is a snippet from the gconf stuff for evolution:
>
> Directly from the file:
> --
>
> uid="1162801071.10728.18@localhost.localdomain" name="Personal"
>
Hi, guys,
This is an expression of dismay of the current practices I see
developing. You may or may not agree, but at least consider the long
term implications.
One of my pet peeves is the lack of formatting on autogenerated files.
Microsoft is one of the worst perpetrators, bu
13 matches
Mail list logo
