Hi,
I'm using Evolution 3.22.2 in up to date Arch system. I have several
accounts in it, and one of them is an Exchange Activesync account using
Evolution-Activesync from Gnome git.
This account is not accessible when I'm inside the corporate network. So
each time Evolution starts, it gives me a
On Sun, 2016-10-23 at 10:12 +0400, Emre Erenoglu wrote:
> I'm using Evolution 3.22.2 in up to date Arch system.
Hi,
there was no release of 3.22.2 yet. :-/ What you use is 3.22.1 with
some pre-release patches, thus some sort of a development version of
the stable release.
It would be nice
On Mon, 24 Oct 2016 12:17:29 +0200, Milan Crha wrote:
>What you use is 3.22.1 with
>some pre-release patches, thus some sort of a development version of
>the stable release.
>
>It would be nice to let the Arch maintainers know to not cause this
>confusion. I do not use Arch, I do not know who they
On Mon, 24 Oct 2016 13:04:37 +0200, Ralf Mardorf wrote:
>On Mon, 24 Oct 2016 12:17:29 +0200, Milan Crha wrote:
>>What you use is 3.22.1 with
>>some pre-release patches, thus some sort of a development version of
>>the stable release.
>>
>>It would be nice to let the Arch maintainers know to not cau
On Monday, October 24, 2016, Milan Crha wrote:
> If I'm not mistaken, then it would be in the evolution-activesync. Fill
> a bug in GNOME's bugzilla against it and hope for a fix.
I'm not sure to agree with this. The error may be coming from the
Evolution-Activesync component (and sometimes fro
On Mon, 2016-10-24 at 16:49 +0400, Emre Erenoglu wrote:
> The error message in Evolution shall be less obtrusive and I think
> such change, if accepted, is within Evolution main window. A small
> icon and a sticky text on the bottom right corner can highlight an
> error situation and clicking it
On Monday, October 24, 2016, Milan Crha wrote:
> it used to be "less intrusive" in the past, in a very similar way you
> outlined above, hiding the message in the status bar. Not many people
> knew that they can get any details about the error at all.
>
Then I would wish it remained like that. A
On Mon, 2016-10-24 at 23:42 +0400, Emre Erenoglu wrote:
> > it used to be "less intrusive" in the past, in a very similar way you
> > outlined above, hiding the message in the status bar. Not many people
> > knew that they can get any details about the error at all.
> >
>
> Then I would wish it re
On Tuesday, October 25, 2016, Patrick O'Callaghan wrote:
> > Left Side: A single line with real status messages, Fetching Message
> > 561/12544 for example. or like out look "all folders up to date", "folder
> > being updated". etc. Clicking it could bring a window with all log
> messages.
>
> Th
On Tue, 2016-10-25 at 12:06 +0400, Emre Erenoglu wrote:
> On Tuesday, October 25, 2016, Patrick O'Callaghan wrote:
>
> >
> > >
> > > Left Side: A single line with real status messages, Fetching Message
> > > 561/12544 for example. or like out look "all folders up to date", "folder
> > > being u
On Tuesday, October 25, 2016, Patrick O'Callaghan wrote:
> On the contrary, often when I suspect something is wrong it's because
> some activity (fetching a message, refreshing a folder, ..) seems to be
> taking too long. If they were flashing by I wouldn't be worried about
> them.
Interesting
On Tue, 2016-10-25 at 12:42 +0400, Emre Erenoglu wrote:
> On Tuesday, October 25, 2016, Patrick O'Callaghan wrote:
> > On the contrary, often when I suspect something is wrong it's because
> > some activity (fetching a message, refreshing a folder, ..) seems to be
> > taking too long. If they were
On Tue, 2016-10-25 at 12:42 +0400, Emre Erenoglu wrote:
> On Tuesday, October 25, 2016, Patrick O'Callaghan wrote:
>
> >
> > On the contrary, often when I suspect something is wrong it's because
> > some activity (fetching a message, refreshing a folder, ..) seems to be
> > taking too long. If t
13 matches
Mail list logo
