On Fri, 2020-01-03 at 18:03 -0800, Ernesto Alfonso wrote:
> I was able to use linphone, which is available in buster.
>
> Ernesto
Linphone is also available from a Flatpak. The newer version is much
better than the one in the Debian main repository.
I was able to use linphone, which is available in buster.
Ernesto
From: Robin Krahl , Fri, 19 Jul 2019 20:12:58 +0200
> Ekiga has been removed as the last upstream release was in 2013, see:
> https://tracker.debian.org/pkg/ekiga
> https://tracker.debian.org/news/1004860/removed-401-9-from-unstable/
>
On Wed 24 Jul 2019 at 17:12:39 (-0400), Greg Wooledge wrote:
> On Wed, Jul 24, 2019 at 11:02:33PM +0200, to...@tuxteam.de wrote:
> > On Wed, Jul 24, 2019 at 03:49:38PM -0500, David Wright wrote:
> >
> > [...]
> >
> > > If I read a file that has an embedded NUL into an editor, I would
> > >
On Tue 23 Jul 2019 at 15:31:12 (-0400), Michael Stone wrote:
> On Tue, Jul 23, 2019 at 02:19:27PM -0500, David Wright wrote:
> > I don't see any NUL characters, but x80 as shown below. I'm reading
> > the cached message that mutt downloaded from an IMAP server. Is that
> > different from you?
>
>
On Wed, Jul 24, 2019 at 11:02:33PM +0200, to...@tuxteam.de wrote:
FWIW, I (somewhat strongly) disagree with Michael here. I'm a
strong proponent of Postel's principle (both sides!).
That's fine, it was a lovely ideal for a different and simpler time.
On Wed, Jul 24, 2019 at 05:12:39PM -0400, Greg Wooledge wrote:
> On Wed, Jul 24, 2019 at 11:02:33PM +0200, to...@tuxteam.de wrote:
> > On Wed, Jul 24, 2019 at 03:49:38PM -0500, David Wright wrote:
> >
> > [...]
> >
> > > If I read a file that has an embedded NUL into an editor, I would
> > >
On Wed, Jul 24, 2019 at 11:02:33PM +0200, to...@tuxteam.de wrote:
> On Wed, Jul 24, 2019 at 03:49:38PM -0500, David Wright wrote:
>
> [...]
>
> > If I read a file that has an embedded NUL into an editor, I would
> > consider it suboptimal if the editor ceased reading any more of the
> > file
On Wed, Jul 24, 2019 at 10:57:09PM +0200, Sven Joachim wrote:
> On 2019-07-24 15:49 -0500, David Wright wrote:
>
> > Where is the definition of NUL as "ignore everything following this
> > character"? AFAICT the mutt manual says nothing about NUL at all.
>
> In the design of the C language,
On Wed, Jul 24, 2019 at 03:49:38PM -0500, David Wright wrote:
[...]
> If I read a file that has an embedded NUL into an editor, I would
> consider it suboptimal if the editor ceased reading any more of the
> file when it hit a NUL.
Vim and Emacs both qualify. Are there other editors? (yes, a
On 2019-07-24 15:49 -0500, David Wright wrote:
> Where is the definition of NUL as "ignore everything following this
> character"? AFAICT the mutt manual says nothing about NUL at all.
In the design of the C language, where NUL is the end of the string as
we know it.
Cheers,
Sven
On Wed, Jul 24, 2019 at 03:49:38PM -0500, David Wright wrote:
> If I read a file that has an embedded NUL into an editor, I would
> consider it suboptimal if the editor ceased reading any more of the
> file when it hit a NUL.
>
> In the same way, I expect mutt and its pager to behave much the
>
On Wed 24 Jul 2019 at 13:51:22 (-0400), Michael Stone wrote:
> On Wed, Jul 24, 2019 at 07:28:11PM +0200, to...@tuxteam.de wrote:
> > On Wed, Jul 24, 2019 at 01:10:49PM -0400, Michael Stone wrote:
> > > On Wed, Jul 24, 2019 at 09:29:47AM -0500, David Wright wrote:
> > > >However, I would not award
On Wed, Jul 24, 2019 at 07:28:11PM +0200, to...@tuxteam.de wrote:
On Wed, Jul 24, 2019 at 01:10:49PM -0400, Michael Stone wrote:
On Wed, Jul 24, 2019 at 09:29:47AM -0500, David Wright wrote:
>However, I would not award +1 to the MUAs that, we are told,
>truncate the message, or even just the
On Wed, Jul 24, 2019 at 01:10:49PM -0400, Michael Stone wrote:
> On Wed, Jul 24, 2019 at 09:29:47AM -0500, David Wright wrote:
> >However, I would not award +1 to the MUAs that, we are told,
> >truncate the message, or even just the line, at the first
> >NUL byte. That could yield a message with a
On Wed, Jul 24, 2019 at 09:29:47AM -0500, David Wright wrote:
However, I would not award +1 to the MUAs that, we are told,
truncate the message, or even just the line, at the first
NUL byte. That could yield a message with a very different sense
from what the sender wrote.
And that is what
On Wed 24 Jul 2019 at 07:10:14 (-0400), rhkra...@gmail.com wrote:
> On Tuesday, July 23, 2019 11:07:37 AM Greg Wooledge wrote:
> > On Tue, Jul 23, 2019 at 07:41:20AM -0700, pe...@easthope.ca wrote:
> > > * From: Brad Rogers
> >
> > Oh, it's this guy again.
> >
> > /me looks at the raw mail
On Tuesday, July 23, 2019 11:07:37 AM Greg Wooledge wrote:
> On Tue, Jul 23, 2019 at 07:41:20AM -0700, pe...@easthope.ca wrote:
> > * From: Brad Rogers
>
> Oh, it's this guy again.
>
> /me looks at the raw mail message with less(1)
>
> * From: Brad Rogers ^@b...@fineby.me.uk^@
>
> Yup.
On Tue, Jul 23, 2019 at 09:35:59PM +0200, to...@tuxteam.de wrote:
On Tue, Jul 23, 2019 at 03:31:12PM -0400, Michael Stone wrote:
On Tue, Jul 23, 2019 at 02:19:27PM -0500, David Wright wrote:
>I don't see any NUL characters, but x80 as shown below. I'm reading
>the cached message that mutt
On Tue, Jul 23, 2019 at 03:38:33PM -0400, Greg Wooledge wrote:
> On Tue, Jul 23, 2019 at 02:19:27PM -0500, David Wright wrote:
> > On Tue 23 Jul 2019 at 11:07:37 (-0400), Greg Wooledge wrote:
> > > Yup. Two NUL bytes in the body of the message. How completely bizarre.
> > >
> > > Apparently
On Tue, Jul 23, 2019 at 02:19:27PM -0500, David Wright wrote:
> On Tue 23 Jul 2019 at 11:07:37 (-0400), Greg Wooledge wrote:
> > Yup. Two NUL bytes in the body of the message. How completely bizarre.
> >
> > Apparently what mutt does is truncate that *line* at the first NUL
> > byte, but then
On Tue, Jul 23, 2019 at 03:31:12PM -0400, Michael Stone wrote:
> On Tue, Jul 23, 2019 at 02:19:27PM -0500, David Wright wrote:
> >I don't see any NUL characters, but x80 as shown below. I'm reading
> >the cached message that mutt downloaded from an IMAP server. Is that
> >different from you?
>
>
On Tue, Jul 23, 2019 at 02:19:27PM -0500, David Wright wrote:
I don't see any NUL characters, but x80 as shown below. I'm reading
the cached message that mutt downloaded from an IMAP server. Is that
different from you?
I see it as x80 in mutt and x00 in the raw file on the imap server. I
On Tue, Jul 23, 2019 at 02:19:27PM -0500, David Wright wrote:
[...]
> I don't see any NUL characters, but x80 as shown below [...]
Oh, that's cute :-)
If I followed along correctly, the questionable mails have
neither Content-Type nor Content-Transfer-Encoding. So the
content type defaults to
On Tue 23 Jul 2019 at 11:07:37 (-0400), Greg Wooledge wrote:
> On Tue, Jul 23, 2019 at 07:41:20AM -0700, pe...@easthope.ca wrote:
> > * From: Brad Rogers
>
> Oh, it's this guy again.
>
> /me looks at the raw mail message with less(1)
>
> * From: Brad Rogers ^@b...@fineby.me.uk^@
>
>
On Tue, Jul 23, 2019 at 11:07:37AM -0400, Greg Wooledge wrote:
> On Tue, Jul 23, 2019 at 07:41:20AM -0700, pe...@easthope.ca wrote:
> > * From: Brad Rogers
>
> Oh, it's this guy again.
>
> /me looks at the raw mail message with less(1)
>
> * From: Brad Rogers ^@b...@fineby.me.uk^@
>
>
On Tue, 23 Jul 2019 07:41:20 -0700
pe...@easthope.ca wrote:
Hello pe...@easthope.ca,
>* From: Brad Rogers * Date: Fri, 19 Jul 2019 19:32:46
>> It was replaced by Empathy.
...
>item are pale gray. Ideas about contacts?
All I know about Empathy is that it replaced Ekiga. I've
On Tue, Jul 23, 2019 at 07:41:20AM -0700, pe...@easthope.ca wrote:
> * From: Brad Rogers
Oh, it's this guy again.
/me looks at the raw mail message with less(1)
* From: Brad Rogers ^@b...@fineby.me.uk^@
Yup. Two NUL bytes in the body of the message. How completely bizarre.
* From: Brad Rogers
On Fri, 19 Jul 2019 09:43:46 -0700
pe...@easthope.ca wrote:
Hello pe...@easthope.ca,
>ekiga is absent from buster.
It was replaced by Empathy.
--
Regards _
/ ) "The blindingly obvious is
/ _)radnever immediately apparent"
Every single one of us
Devil
On 2019-07-19 09:43:46, pe...@easthope.ca wrote:
> ekiga is absent from buster. Something involving ssl/tls?
Ekiga has been removed as the last upstream release was in 2013, see:
https://tracker.debian.org/pkg/ekiga
Hello again,
ekiga is absent from buster. Something involving ssl/tls?
I guess it will surface sooner or later. Any suggestions
for the interim? Add stretch to /etc/apt/sources.list
and try that?
Thanks, ... P.
--
https://en.wikibooks.org/wiki/Oberon
Tel: +1 604 670 0140
32 matches
Mail list logo
