Its probable that other users of file servers have them mounted (or whatever
the Windows word is) so they access by something like `//server/foo/file.blah`.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/3808#discussioncomment-8962208
You are
Oh no, not a bit. Just because it's a pain for _me_ doesn't mean that it's not
perfectly fine for everyone else using the system. I went out after I wrote
that and read through the PR, I saw where the dev mentioned the buggy and
changed api for Windows calls.
If it's an easy add, it would
> Oh, as a follow up, apparently it's not possible to open up a network
> location without first mapping the drive in Windows. […] And the list of
> "Available Protocols" and "Prefix"es is blank.
It *might* be that there are extensions that are not packaged with Geany (like
some GVFS
Closed #3808 as resolved.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/3808
You are receiving this because you are subscribed to this thread.
Message ID:
Reopened #3808.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/3808
You are receiving this because you are subscribed to this thread.
Message ID:
Oh, as a follow up, apparently it's not possible to open up a network location
without first mapping the drive in Windows. Typically you can just go to
"\\192.168.0.xxx\share" in the dialog, however not any longer. Also
"smb://192.168.0.xxx" doesn't work with Ctrl-L (it will not accept the
Closed #3808 as resolved.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/3808
You are receiving this because you are subscribed to this thread.
Message ID:
Thank you!
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/3808#discussioncomment-8960192
You are receiving this because you are subscribed to this thread.
Message ID:
There are others, but I'm not aware of a proper documentation on this… quick
search yields https://winaero.com/gtk-open-save-file-dialog-keyboard-shortcuts/
which isn't canonical but seems to list at least most of it.
--
Reply to this email directly or view it on GitHub:
Ctrl-F works to do it, thank you! Btw, any other shortcuts that aren't listed
apart from those two?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/3808#discussioncomment-8957105
You are receiving this because you are subscribed to this thread.
> But with the new browser when I hit \*, my system just goes "Bong" with an
> error sound
After using Ctrl+L? There are actually 2 ways to search/filer:
* Ctrl+L: location entry, e.g. you can type a file path, and it
should provide completion
* Ctrl+F (or just typehead, e.g. start typing in
That's probably it. But with the new browser when I hit \*, my system just
goes "Bong" with an error sound
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/3808#discussioncomment-8955912
You are receiving this because you are subscribed to this
Ah, ok, wildcards, indeed I didn't see that. However, although I didn't know
about the feature (thanks :slightly_smiling_face: ) it *does* work for me: if I
type `*file` it shows me a list of suggestions matching that (and the wildcard
acts as one). It's not a *filter* as it doesn't change
Ctrl-L lets you type in a path, but it won't accept wildcards like *. So
again, I was able to type *file* to show all files in the current path that
contain "file" in the filename.
--
Reply to this email directly or view it on GitHub:
> I just recently went to v2 from v1.36 (I believe), and I just realized that
> there's not an option any longer to allow filtering of files based on
> filename. So if you're in a directory with thousands of files, and misc
> filenames, you need to scroll through to find the correct file
15 matches
Mail list logo
