No, can we change the default key trigger is what I am asking, so users
won't have to do it themselves
On Tue, Sep 29, 2015 at 4:52 PM, Kwaadpepper <email address hidden>
wrote:
> I believe this is no bug since you can change the trigger key
> combination for synapse right ?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1493116
>
> Title:
> Default ctrl+space hardware key trigger conflict
>
> Status in Synapse:
> New
>
> Bug description:
> The trigger is ctrl+space and it meddles with the existing triggers
> like auto complete for eclipse
>
> we can change it to ctrl + shift + space
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/synapse-project/+bug/1493116/+subscriptions
>
No, can we change the default key trigger is what I am asking, so users
won't have to do it themselves
On Tue, Sep 29, 2015 at 4:52 PM, Kwaadpepper <email address hidden>
wrote:
> I believe this is no bug since you can change the trigger key /bugs.launchpad .net/bugs/ 1493116 /bugs.launchpad .net/synapse- project/ +bug/1493116/ +subscriptions
> combination for synapse right ?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Default ctrl+space hardware key trigger conflict
>
> Status in Synapse:
> New
>
> Bug description:
> The trigger is ctrl+space and it meddles with the existing triggers
> like auto complete for eclipse
>
> we can change it to ctrl + shift + space
>
> To manage notifications about this bug go to:
> https:/
>