I agree that I can change the shortcut in my machine, my request was to
make ctrl + shift + space as the default trigger :)
In the interest of all the users!
On Tue, Sep 29, 2015 at 6:58 PM, Kwaadpepper <email address hidden>
wrote:
> Synapse is saving the config file on close event (when synapse is
> exiting).
>
> you can change you config.json file to use
>
> "activate" : "<Shift><Control>space",
> instead of
> "activate" : "<Control>space",
>
> --
> 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
>
I agree that I can change the shortcut in my machine, my request was to
make ctrl + shift + space as the default trigger :)
In the interest of all the users!
On Tue, Sep 29, 2015 at 6:58 PM, Kwaadpepper <email address hidden>
wrote:
> Synapse is saving the config file on close event (when synapse is <Control> space", /bugs.launchpad .net/bugs/ 1493116 /bugs.launchpad .net/synapse- project/ +bug/1493116/ +subscriptions
> exiting).
>
> you can change you config.json file to use
>
> "activate" : "<Shift>
> instead of
> "activate" : "<Control>space",
>
> --
> 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:/
>