Giter VIP home page Giter VIP logo

gnome-shell-extension-sshsearch's People

Contributors

brot avatar eonpatapon avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

gnome-shell-extension-sshsearch's Issues

Extension doesn't work of value host is not capitalized

Hi,

first of all thanks for this really helpful shell extension. I found two "problems", I will create another issue for the secound problem.

System: Ubuntu 11.10 64bit with gnome-shell 3.2.1-0ubuntu1 (from proposed), installed your extension from extension.gnome.org

If the the keyword "host" in .ssh/config begins with a small h, then the entry is not parsed and therefore doesnt show up in the search provider. Here an example:

host gnome-test
User test
Hostname test.tld

Update to v3.8.1

Changing the shell version in json doesn't help...

Looking Glass claims "Search.SearchProvider" is not defined.

when several hostnames are defined, hostname is one string

Hi,

System: Ubuntu 11.10 64bit with gnome-shell 3.2.1-0ubuntu1 (from proposed), installed your extension from extension.gnome.org

When several hostnames are defined in a single rule, the search provider will take the whole name and wont recognize each hostname seperately:

Example

Host 192.168.11.11 192.168.11.13 192.168.11.15 192.168.11.16
User root
ProxyCommand ssh -q -a -x gateway nc %h 22

Trough the shell I can connect to each machine seperately via ssh 192.168.11.11, the search provider unfortunately gets "192.168.11.11 192.168.11.13 192.168.11.15 192.168.11.16" as a single machine.

only 1 line of results shown

I only get 1 line but I do have more results which didn't get viewed - is this limited by the extension or just a gnome setting somewhere?

Search does not show all results

Hi, first of all, nice extension, thanks!

I noticed that when number of results does not fit one "line" in overview, exceeding results will not be shown...
If I narrow the search, the fewer results will then show up.
Ex:
192.168.1. - some results will not be shown. No enough place for all results.
192.168.1.10 - results in fewer matches, there fore the missing results will can be seen.

Is it a problem in my overview configuration, or a issue in the extensions?!

Thank you in advance.
BR, careca

Please update to Gnome 3.12

Hello :)

this one of the best extension for the gnome-shell. I love it. It is possible to update it for gnome 3.12? I change the versionnumber in metadata.json, but it does not work. So i think it's more advanced. Maybe a lot of things in gome-shell where changed. I'am no a developer, please excuse me ;)

Best Regards
boospy

Is it possible to search in the the `Alt+F2` run dialog?

Thanks for great extension!

As triggering the overview is quite slow, I was thinking if the search mechanism could be also used when pressing Alt+F2 in gnome-shell to trigger the run dialog. So after pressing Alt+F2 the run dialog shows up very quickly where I can start commands in my $PATH, but it would be cool if the hostnames would be found too.

This questions is rather a gnome-shell question I suppose, but I would be really thankful if anyone could point me to a good direction. Is it possible?

Fails if org.gnome.desktop.default-applications.terminal exec is not set

Ubuntu 13.10 with Gnome Shell 3.8.4:

Entries within SSH config are found, but no icons are displayed, only text.

If an entry is chosen, a terminal starts but with local ~ as directory. SSH command is not executed, but no error occurs.

gnome-terminal --command "ssh host" works, however, when issued from the command line.

I tried to add some logging to give more information, but failed miserably. Sorry for that.

filter out duplicate search results

My ~/.ssh/config mentions several hosts by name. Each of these generally appears in ~/.ssh/known_hosts as well. The extension finds both mentions, includes both in its search results, and therefore the same host appears twice when I search in GNOME Shell. That is not very useful, since selecting either will do exactly the same thing.

Perhaps GNOME Shell should be removing duplicates? It isn’t, and I don’t know if it ever promised that it would. Barring a change there, this extension should filter out duplicates itself. Presumably this would happen somewhere near the end of _getResultSet, by modifying the results array just before calling setResults.

Terminal profile per destination?

Is there a way to select a terminal profile per destination?

I like to have one terminal profile for local and miscellaneous shell account terminals and another (visually different) profile for e.g. production web servers. That helps me avoid doing stupid things on the wrong hosts ... :-)

So either if gnome-term can be made to recognize the commands this extension uses and select different profiles by itself (maybe an existing feature in gnome-terminal that I just don't know about?) or if gnome-shell-extension-sshsearch can be made to tell the terminal what profile to use, maybe based on directives / comments in .ssh/config?

Doesn't look at /etc/ssh/ssh_known_hosts

I often put a bunch of known hosts in /etc/ssh/ssh_known_hosts. It would be useful for the extension to look there as well. Note that some systems name this file /etc/ssh_known_hosts instead.

Terminal just opens, no command being executed

Given is a SSH configuration like this:

Host foobar
  HostName foo.bar
  Port 123
  User justTheUser

When I open the GNOME Dash
and type in the search the name "foobar"
and press Enter or choose the upcoming SSH-Connection,
then it should open the terminal
and login at the server.


The last step fails.
The terminal is being opened but there is no action taken to login at the given SSH-config.

What information to you need to track down this issue?

Do not parse lines which are commented out (starting with `#`)

I have quite a few hosts commented out in my ~/ssh/config file which are not needed most of the time. Once a year I enable those for a week or so.

Would it require much coding to skip the commented out lines in the config file? If so, I would keep this simple by removing those lines and keeping just in a backup dir, so pls feel free to close this, if you think this would not make much sense.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.