On 2013-06-20, Frank Reininghaus wrote:
> That would be great. I don't really know when will be the next time
> Thanks for your help and best regards,
Done.
Regards,
Sune
Hi,
2013/6/20 Ivan Čukić:
>
>> implemented this at a time when Ivan still refused to acknowledge that
>> there is a bug in his plugin at all. There was no real solution in
>
> From this point on, I'm ignoring this discussion.
>
> I have never said that the plugin is not the reason for the bug 3145
> implemented this at a time when Ivan still refused to acknowledge that
> there is a bug in his plugin at all. There was no real solution in
>From this point on, I'm ignoring this discussion.
I have never said that the plugin is not the reason for the bug 314575, I just
explained why it is blo
On Donnerstag, 20. Juni 2013 14:13:06 CEST, Frank Reininghaus wrote:
Yes, that's what I meant, but im my experience, changing the status of
a bug to NEEDSINFO is in most cases equivalent to closing, because the
reporter will not respond, and the bug stays in the NEEDSINFO state
forever.
The bu
Hi Sune,
2013/6/20 Sune Vuorela:
>>> so Frank, please, pretty please, can you reconsider?
>>
>> I see that Ivan rewrote the plugin and that it does at least not do
>> anything fishy any more before the context menu is shown. I also
>> understand that people who do not have to deal with the bug rep
Hi Sebastian,
2013/6/20 Sebastian Kügler:
>> > Why not just ask to reproduce with plugins disabled, then enable plugin
>> > for
>> > plugin, and reassign the bug accordingly?
>>
>> I've tried that often enough. Most bug reporters never respond.
>> Therefore, I think it's better to close the report
On 2013-06-20, Frank Reininghaus wrote:
> I admit that the current "solution" is an ugly hack. But it was never
> meant to be an "arms race". Please note that I proposed and
> implemented this at a time when Ivan still refused to acknowledge that
> there is a bug in his plugin at all. There was no
Hi Frank,
On Thursday, June 20, 2013 12:39:00 Frank Reininghaus wrote:
> 2013/6/20 Sebastian Kügler:
> > Hi Frank,
> >
> > On Thursday, June 20, 2013 10:51:58 Frank Reininghaus wrote:
> >> Moreover, I will from now on:
> >>
> >> (a) Close all "Dolphin freezes/crashes/formats my hard drive when
>
Hi Sebastian,
2013/6/20 Sebastian Kügler:
> Hi Frank,
>
> On Thursday, June 20, 2013 10:51:58 Frank Reininghaus wrote:
>> Moreover, I will from now on:
>>
>> (a) Close all "Dolphin freezes/crashes/formats my hard drive when
>> right-clicking a file" bug reports immediately, unless the bug
>> descr
Hi Frank,
On Thursday, June 20, 2013 10:51:58 Frank Reininghaus wrote:
> Moreover, I will from now on:
>
> (a) Close all "Dolphin freezes/crashes/formats my hard drive when
> right-clicking a file" bug reports immediately, unless the bug
> descrition states that the issue persists when all plugin
Hi,
2013/6/19 Sune Vuorela:
> On 2013-06-19, Thomas Lübking wrote:
>>> If I was a plugin developer here, I would of course think my plugin
>>> should be enabled by default and thus in my ctor call
>>> setEnabledByDefault(true)
>>
>> I would suggest to leave the path of plugin enabling as solution
Hi,
2013/6/19 Thomas Lübking:
> On Mittwoch, 19. Juni 2013 20:21:41 CEST, Sune Vuorela wrote:
>>
>> On 2013-06-17, Frank Reininghaus wrote:
>>>
>>> Yes, it can block for random reasons, and this is why making D-Bus
>>> calls in the code that is executed before the context menu is shown is
>>> una
On 2013-06-19, Thomas Lübking wrote:
>> If I was a plugin developer here, I would of course think my plugin
>> should be enabled by default and thus in my ctor call
>> setEnabledByDefault(true)
>
> I would suggest to leave the path of plugin enabling as solution asap - it's
> not a solution at al
On Mittwoch, 19. Juni 2013 20:21:41 CEST, Sune Vuorela wrote:
On 2013-06-17, Frank Reininghaus wrote:
Yes, it can block for random reasons, and this is why making D-Bus
calls in the code that is executed before the context menu is shown is
unacceptable IMHO.
I agree with the problem. But the
On 2013-06-17, Frank Reininghaus wrote:
> Yes, it can block for random reasons, and this is why making D-Bus
> calls in the code that is executed before the context menu is shown is
> unacceptable IMHO.
I agree with the problem. But the issue is to *fix* kactivities to not
do something insane. Th
在 2013年6月10日 星期一 19:42:36，Albert Astals Cid 写道：
> El Dilluns, 10 de juny de 2013, a les 15:56:16, Frank Reininghaus va
escriure:
> > Hi Albert,
> >
> > thanks for the quick reply.
> >
> > 2013/6/9 Albert Astals Cid:
> > > El Diumenge, 9 de juny de 2013, a les 09:22:10, Frank Reininghaus va
>
>
Hi,
2013/6/14 Thomas Lübking:
> On Donnerstag, 13. Juni 2013 16:36:31 CEST, Frank Reininghaus wrote:
>>
>> Hi,
>>
>> sorry for the late reply.
>
>
> And sorry myself for similar reasons ;-)
>
>>> 2013/6/10, Frank Reininghaus:
>>
>> time explaining users why reassigning the bug away from Dolphin ma
On Donnerstag, 13. Juni 2013 16:36:31 CEST, Frank Reininghaus wrote:
Hi,
sorry for the late reply.
And sorry myself for similar reasons ;-)
2013/6/10, Frank Reininghaus:
time explaining users why reassigning the bug away from Dolphin makes
sense ("No, that's impossible. I don't use Activiti
Hi,
sorry for the late reply.
2013/6/10 Albert Astals Cid:
> El Dilluns, 10 de juny de 2013, a les 15:56:16, Frank Reininghaus va escriure:
> Was thinking yesterday that maybe we want to involve some of the usability
> guys? Explain the problem and see if they come up with a nice idea that has
>
Hi,
sorry for the late reply.
2013/6/10 Thomas Lübking:
> 2013/6/10, Frank Reininghaus:
>
>> It was indeed an *extremely* frustrating experience for me to find out
>> that code which had (to my knowledge) been written without any kind of
>> review could be installed and run on the machine of ever
El Dilluns, 10 de juny de 2013, a les 15:56:16, Frank Reininghaus va escriure:
> Hi Albert,
>
> thanks for the quick reply.
>
> 2013/6/9 Albert Astals Cid:
> > El Diumenge, 9 de juny de 2013, a les 09:22:10, Frank Reininghaus va
escriure:
> >> Hi Albert,
> >>
> >> thanks for your comments.
> >>
2013/6/10, Frank Reininghaus :
> It was indeed an *extremely* frustrating experience for me to find out
> that code which had (to my knowledge) been written without any kind of
> review could be installed and run on the machine of every Dolphin user
> out there, and that the bug reports which were
Hi Albert,
thanks for the quick reply.
2013/6/9 Albert Astals Cid:
> El Diumenge, 9 de juny de 2013, a les 09:22:10, Frank Reininghaus va escriure:
>> Hi Albert,
>>
>> thanks for your comments.
>>
>> 2013/6/8 Albert Astals Cid:
>> > El Divendres, 7 de juny de 2013, a les 17:40:29, Frank Reiningha
El Diumenge, 9 de juny de 2013, a les 09:22:10, Frank Reininghaus va escriure:
> Hi Albert,
>
> thanks for your comments.
>
> 2013/6/8 Albert Astals Cid:
> > El Divendres, 7 de juny de 2013, a les 17:40:29, Frank Reininghaus va
> >
> > escriure:
> >> Hi everyone,
> >
> > Hi
> >
> >> I've recen
Hi Albert,
thanks for your comments.
2013/6/8 Albert Astals Cid:
> El Divendres, 7 de juny de 2013, a les 17:40:29, Frank Reininghaus va
> escriure:
>> Hi everyone,
>
> Hi
>
>> I've recently implemented a mechanism that allows developers of
>> KAbstractFileItemActionPlugins to state that their pl
El Divendres, 7 de juny de 2013, a les 17:40:29, Frank Reininghaus va
escriure:
> Hi everyone,
Hi
> I've recently implemented a mechanism that allows developers of
> KAbstractFileItemActionPlugins to state that their plugin should not
> be shown in file-management related context menus by defaul
Hi everyone,
I've recently implemented a mechanism that allows developers of
KAbstractFileItemActionPlugins to state that their plugin should not
be shown in file-management related context menus by default [1].
I've been thinking again about this approach again this week, and now
I think that it
27 matches
Mail list logo
