Default ctrl+space hardware key trigger conflict

[Suraj Patil]

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

[Jérémy Munsch (jeremy-munsch)]

I believe this is no bug since you can change the trigger key combination for synapse right ?

[Suraj Patil (srjptl2050)]

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
>

[Jérémy Munsch (jeremy-munsch)]

When you change the key, synapse is create a json file in ~/.config/synapse/config.json
it contains like
{
  "ui" : {
    "global" : {
      "ui-type" : "virgilio"
    },
    "shortcuts" : {
      "activate" : "<Control>space",
      "execute" : "Return",
      "execute-without-hide" : "<Shift>Return",
      "delete-char" : "BackSpace",
      "alternative-delete-char" : "Delete",
      "next-match" : "Down",
      "prev-match" : "Up",
      "first-match" : "Home",
      "last-match" : "End",
      "next-match-page" : "Page_Down",
      "prev-match-page" : "Page_Up",
      "next-category" : "Right",
      "prev-category" : "Left",
      "next-search-type" : "Tab",
      "prev-search-type" : "<Shift>ISO_Left_Tab",
      "cancel" : "Escape",
      "paste" : "<Control>v",
      "alt-paste" : "<Shift>Insert",
      "exit" : "<Control>q"
    }
  }
}

To find it on you distribution you could try a : cd ~; find . -name config.json

[Jérémy Munsch (jeremy-munsch)]

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",

[Suraj Patil (srjptl2050)]

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
>

[Jérémy Munsch (jeremy-munsch)]

Ok, sorry I misunderstood.

[Suraj Patil (srjptl2050)]

Are we going to change the shortcut? It'll be better because atrl+space has
conflicts :(

Also I wanted to ask how about redesigning synapse to make it as sexy as
Spotlight of Mac?

On Tue, Sep 29, 2015 at 8:49 PM, Kwaadpepper <email address hidden>
wrote:

> Ok, sorry I misunderstood.
>
> --
> 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
>

[Jérémy Munsch (jeremy-munsch)]

My guess is that it is not likely going to happen because the proposed shortcut is not simplier, it would be a broken change for the user experience, also it is a conflict with another software. You could propose a change on a Readme file maybe but that it i guess.

As for redesigning this is offtopic, but please submit your own theme with a merge request, you could try to start from the view-virgilio.vala file.

[Suraj Patil (srjptl2050)]

No no, the proposed shortcut might not be simple, but your current shortcut
is ctrl + space which is used in few applications already, which breaks the
UX of your current users anyways, try using synapse and eclipse, it is
frustrating because every time you try to do auto complete synapse pops up.
totally annoying and it isn't just eclipse too.

On Tue, Sep 29, 2015 at 9:12 PM, Kwaadpepper <email address hidden>
wrote:

> My guess is that it is not likely going to happen because the proposed
> shortcut is not simplier, it would be a broken change for the user
> experience, also it is a conflict with another software. You could
> propose a change on a Readme file maybe but that it i guess.
>
> As for redesigning this is offtopic, but please submit your own theme
> with a merge request, you could try to start from the view-virgilio.vala
> file.
>
> --
> 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
>