[3691] in BarnOwl Developers
Re: [barnowl] Perl logging (#54)
daemon@ATHENA.MIT.EDU (Jason Gross)
Sat Jan 4 14:37:58 2014
Date: Sat, 04 Jan 2014 11:37:55 -0800
From: Jason Gross <notifications@github.com>
Reply-To: barnowl/barnowl <reply+i-1212393-313039cd867d577b5721069e10330b49395747f8-4475081@reply.github.com>
To: barnowl/barnowl <barnowl@noreply.github.com>
Cc: barnowl-dev email-only account <barnowl-dev@mit.edu>
In-Reply-To: <barnowl/barnowl/pull/54@github.com>
----==_mimepart_52c86313647e9_5526f99d041957db
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
> No, you=E2=80=99re missing the point. It=E2=80=99s not about appropriat=
e names, it=E2=80=99s about compatibility. Someone who upgrades BarnOwl w=
ithout carefully reading the release notes should not suddenly find that =
their messages which used to be logged now get dropped on the floor.
I'm not sure that having such a "compatibility mode" is worth the trouble=
. I've made 7313c14, which uses `~/zlog/missing` (but should be easily c=
ustomizable), and complains very noisily, and I'm unhappy with the code c=
omplexity. How do you feel about the (not yet implemented) alternative w=
hich adds `aim:log-to-people` and `jabber:log-to-people` variables which =
are on by default, and reproduce the old behavior (with much simpler code=
than 7313c14), and mentions that these are compatibility frobs and that =
if you turn them off, you need to make the appropriate directories? Anot=
her alternative (which I think I might prefer) is to attempt to make the =
directories if they don't already exist.
---
Reply to this email directly or view it on GitHub:
https://github.com/barnowl/barnowl/pull/54#issuecomment-31586637=
----==_mimepart_52c86313647e9_5526f99d041957db
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<blockquote>
<p>No, you=E2=80=99re missing the point. It=E2=80=99s not about appropria=
te names, it=E2=80=99s about compatibility. Someone who upgrades BarnOwl =
without carefully reading the release notes should not suddenly find that=
their messages which used to be logged now get dropped on the floor.</p>=
</blockquote>
<p>I'm not sure that having such a "compatibility mode" is worth the trou=
ble. I've made <a href=3D"https://github.com/barnowl/barnowl/commit/7313=
c14" class=3D"commit-link"><tt>7313c14</tt></a>, which uses <code>~/zlog/=
missing</code> (but should be easily customizable), and complains very no=
isily, and I'm unhappy with the code complexity. How do you feel about t=
he (not yet implemented) alternative which adds <code>aim:log-to-people</=
code> and <code>jabber:log-to-people</code> variables which are on by def=
ault, and reproduce the old behavior (with much simpler code than <a href=
=3D"https://github.com/barnowl/barnowl/commit/7313c14" class=3D"commit-li=
nk"><tt>7313c14</tt></a>), and mentions that these are compatibility frob=
s and that if you turn them off, you need to make the appropriate directo=
ries? Another alternative (which I think I might prefer) is to attempt t=
o make the directories if they don't already exist.</p>
<p style=3D"font-size:small;-webkit-text-size-adjust:none;color:#666;">&m=
dash;<br>Reply to this email directly or <a href=3D'https://github.com/ba=
rnowl/barnowl/pull/54#issuecomment-31586637'>view it on GitHub</a>.<img s=
rc=3D'https://github.com/notifications/beacon/4475081__eyJzY29wZSI6Ik5ld3=
NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcwNDM5NzA3NSwiZGF0YSI6eyJpZCI6MjI3OTE3NzN=
9fQ=3D=3D--6da98225ea9f760d86342f9dcf5f1c935277ef36.gif' height=3D'1' wid=
th=3D'1'></p>=
----==_mimepart_52c86313647e9_5526f99d041957db--
