Re: [Github-comments] [geany/geany] Too Many Filetypes in Open Dropdown! How can I shorten list? (#2296)
Thank you for all responses. Since my last post, I did look at the source code and found out that all those file type are, in fact, hardcoded into the system, so there is no way to remove them other than edit and rebuild the source. LarsGit233 summarizes the search process I went throught quite well. Sorry I didn't post my disappointment earlier. Scrolling through 30 types when you only use 5 is an unacceptable solution. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2296#issuecomment-535275864
Re: [Github-comments] [geany/geany] PRIMARY selection should be stable (#2323)
The Scintilla editing widget that Geany uses defines a selection as between the current cursor and the anchor, and clicking in the widget moves _both_ the anchor and cursor to the same place so there is no longer any selection. So its hard to see how it would work since X11 (not Unix, its just that Unix usually uses X11) has no actual clipboard to keep the selection on, its requested dynamically when the middle click happens. This is the same as all the editors I have available to test, the one outlier is this edit here in the browser, in Chromium, which explains why atom does it since electron is Chromium. Its probable that Chromium isn't actually using the X11 paste on middle click and is doing it itself. And the cause of your ending up pasting in the wrong place may be that middle click pastes where the X11 cursor is, not where the Scintilla cursor is. That happens even here in the browser. Of course its hard to ensure that cursor is exactly where you want it, since it can be on any pixel, and has to be mapped to the character position. Scintilla grew up on Windows, so as an baby editor it only had copy/paste and thats still its main way of working since the paste goes to the editing widget cursor position that is stable and well defined. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2323#issuecomment-535266907
Re: [Github-comments] [geany/geany] Add AutoIt syntax highlighting and Ctags parser for AutoIt (#1752)
@Skif-off pushed 30 commits. 21b06d1e4bf18f2cab137ab08a976dbf14274d58 prefer XDG_RUNTIME_DIR over /tmp for the socket (#) 7214a646f8b467f5c790c786bcc4c2f8b4226e21 Update ja.po: "Appearance" "外観"→"出現" (#2255) 46d5e7542b8396ed593f2e319f71d153a67684dc Add support for fractional font sizes c29bf208530f4a852c176afd6b8f65e1436c4611 Show the GTK/GLib versions in about dialog (#2163) ec0e11ca040ef142ca1ab09f34951bf809b8839d [docs] Move error_regex section to [build-menu]; add filetype example aa90ea7035d0c01d1c5f00d97a0820a9daefac02 build.c: Replace ASSIGNIF inline macro with assign_cmd function d19f7719a5c3c81b4fa87df4bd2c7d8f3959e117 Add Groovy custom filetype (#2188) d80e36e85a031fc266fe200add05f0626a0696ad TypeScript syntax highlighting 434cfe580b0fdf4cf4cd02f4f7cb0bbbfa922f5e build.h: Move GBO_TO_* macros to build.c f088e7bdf62b706cb3a3970cf2f937a7e7408d66 Move GEANY_GBO_COMPILE etc to build.c 0ce5d5484e39edc25bc996cc0bf01f5bdc2b5221 build.c: Remove g_ptr_array_foreach with gpointer user_data & update HACKING (#2270) c88c27e2d22dbff72488d8a57a825830fb833682 Fix broken markup in HACKING 64a32db5e1d202b9055dd90dab335f7c2afa62c0 tests: unit test for some util strv functions 30a486d62462ad2bf34ac7af48547053f7167441 utils: fix suboptimal elipsis substitution by utils_strv_shorten_file_list() 72d9f378e0de976a6d3d9b5fb3107c1979f8895b utils: refactor utils_strv_shorten_file_list() and friends 4b4a41e7f54eb1de3941854fc66f53811fb70ef9 utils: move utils_strv_shorten_file_list() out of GEANY_PRIVATE 746697ab07e87077758c0b71280cf90cd01a5146 Merge pull request #2262 from kugel-/fix-1445 411aa99c00f6af1156f0a7d891dfcf0ed072e476 configure: check for realpath function now MSYS2 has it (#2263) 21488bc4b225e777130daa72d2470e8da87970f8 Update po files for string freeze of 1.36 0a9d076c688e72dc5e6211e287e00933cd6a3f44 Small update of the French translation a4e27a04a96fa6f80ee78927da18569a91837c0c Update version info for French translation 9e1bccc1c4b057eb4a2f14066ac6f46aa8f7e7c2 Small update of German translation b52a1ef8fd5e201d35921002fa4549fa7b5a4ac1 Update of NEWS for translation updates since 1.35 736aa5566aa66a7847735361f8a346316c68526d Update of Japanese translation 94a944114ba3d9db4e442472c44127fecf642a42 Update of Portuguese translation 64bd04b1bfb5d2218eee96afccab9c37d59edebb Update danish translation to 1.36 (#2313) 751644ccc7264d50180c2d99c7ddc2a8dea4c32f it.po for 1.36 (#2311) c669e69f000ca1b73ac8729f7614374200dfb43c Updated Danish and Italian translation 328e39a6a419cbf653380716f41916fb96106cbe Update of Spanish translation 96dfbc14e2e38703e289fa41306bf5995597c379 Add AutoIt syntax highlighting and Ctags parser for AutoIt -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/geany/geany/pull/1752/files/1a1af339fc370ec5451eadd43c332f036e03380c..96dfbc14e2e38703e289fa41306bf5995597c379
Re: [Github-comments] [geany/geany] Enhancement - Vertical Editing Sequential Numbering (#2317)
Voting? Why is it that everyone wants to cut off an option thats useful in some situations in favour of an option thats useful in others, as I said on #850 why not have __BOTH__ and which is default can be set from an option. [start rant] I'm getting sick of people who assert that their preferred way is the only way of doing something and all other ways must be suppressed because _they_ want it that way or because some other tool does it that way. It feels like every second pull request is to drop something useful in some use cases and replace it with something thats useful in a _different_ set of use-cases. Somebody always has to lose. Folks lets try adding value here, not slicing it ever thinner so the tools are only useful for a small for a narrower and narrower user space. [end rant, sorry @AdamDanischewski to hijack your PR] -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2317#issuecomment-535196845
Re: [Github-comments] [geany/geany] Enhancement Request - Multiselect Multipaste Option (#850)
> Sorry for seeming silly, but what are the two options? When there is a rectangular selection and a single item on the clipboard the choice is to paste the single item into the first row of the selection or to repeat the single item in every row of the selection. Although from #2317 comes the suggestion that if the clipboard is multi-line that successive lines get pasted into successive rows of the selection, so now there are three options :grin: -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/850#issuecomment-535192035
[Github-comments] [geany/geany-plugins] vimode o/O not respecting indent settings (#910)
Hi, This ones a bit simpler, basically when I press o (lowercase) in vimode, in geany it sends the cursor to the very beginning of the newline below, in vim it would respect the auto indent and put the cursor where it should be, just like hitting return at the end of a line in geany vimode. The same happens with O (uppercase), although it is the line above, which is correct, just without the indent again. I again offer my services if this is something people want. Thanks, Lukas -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/issues/910
[Github-comments] [geany/geany-plugins] dw/cw incorrect behaviour (#909)
Hi,
I use vim quite a lot and noticed a few incorrect behaviours, dw and cw being
one.
I'll denote the cursor as a double quote ("), before a letter means it's on
that letter.
In geany vimode the following line int the function block:
`void foo(BarClass *pointer) {
std::"cout << pointer->bar_func() << std::endl;
}`
pressing dw or cw would yield:
`void foo(BarClass *pointer) {
std::"pointer->bar_func() << std::endl;
}`
in vim either would yield: (it deletes up to some special characters, not the
next word)
`void foo(BarClass *pointer) {
std::"<< pointer->bar_func() << std::endl;
}`
Another example, start again here, with cursor before pointer:
`void foo(BarClass *pointer) {
std::cout << "pointer->bar_func() << std::endl;
}`
geany yields:
`void foo(BarClass *pointer) {
std::cout << "bar_func() << std::endl;
}`
vim yields:
`void foo(BarClass *pointer) {
std::cout << "->bar_func() << std::endl;
}`
Geany vimode also treats dw and cw the same in all cases (apart from dw staying
in normal mode and cw entering insert mode, which is correct). In the below
example, cursor on B of BarClass:
`void foo("BarClass *pointer) {
std::cout << pointer->bar_func() << std::endl;
}`
for both, geany would yield:
`void foo("pointer) {
std::cout << pointer->bar_func() << std::endl;
}`
dw in vim would yield: (asterisk remains)
`void foo("*pointer) {
std::cout << pointer->bar_func() << std::endl;
}`
cw would yield: (extra space, so when typing new word, space is already there)
`void foo(" *pointer) {
std::cout << pointer->bar_func() << std::endl;
}`
It's worth noting that the special character seem to be specific, so for
example underscore is treated as part of the word in vim:
`void foo(BarClass *pointer) {
std::cout << pointer->"bar_func() << std::endl;
}`
dw or cw in vim becomes: (deletes underscore too)
`void foo(BarClass *pointer) {
std::cout << pointer->"() << std::endl;
}`
These seem minor but it is much more often the case that the Alphanum
characters and underscore are the ones that the user is considering the 'word'
and wants to delete, having to re-type the operators such as '<<' or '-' or '>'
etc etc is not the intention.
If it is likely that these changes will get integrated into vimode I would like
to offer my services since I work with c and c++ and vim, I think I could get
it working just right. Am I ok to dig in?
Thanks,
Lukas
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/909
Re: [Github-comments] [geany/geany] Enhancement Request - Multiselect Multipaste Option (#850)
> > Its not exactly "mind reading" to presume that someone wants a single row > > pasted into every row of a multi-line selection. An option being required > > to turn off this behavior? If you really want to paste to a single line to > > a single row then don't do a multi-line select beforehand - simply put the > > cursor where you want and paste it like normal. > > The problem with this argument is that both sides think their option is > obvious and clearly the correct one and can't understand the other mob. > > In fact they are both right, each solution is useful at times, so as I > suggest, why not just have two pastes, one to paste single, and one to paste > multiple. Then the only argument is which is default . And that could be > solved with the option. Sorry for seeming silly, but what are the two options? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/850#issuecomment-535114840
Re: [Github-comments] [geany/geany] Enhancement - Vertical Editing Sequential Numbering (#2317)
I still strongly think that a single-line copy should paste repeatedly in as many lines selected as they are. That's why you did the multi-line selection after copying and that's the quickest way to append certain text to lines that are similar in structure (like tabular data for instance). I think this would make the multi-line selection much more useful, at least for me. Another good point to make it work this way is that it would be consistent with the behaviour of many other popular editors. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2317#issuecomment-535111758
Re: [Github-comments] [geany/geany] Enhancement - Vertical Editing Sequential Numbering (#2317)
@ntrel Yea, I played around with it before and it's expected behavior. I kind of think multi-paste should work the way @Akronix mentioned in #850. If you have one line and then make a vertical selection (rectangular selection) that it multi-pastes across the entire selection but there's still some debate about it. Maybe a vote would help? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2317#issuecomment-535054702
Re: [Github-comments] [geany/geany] Prefs dialog: Disable overridden pref widgets when project is open (#2316)
@ntrel pushed 1 commit. 32f99badc0db3a99285ad359d341aa86b98a22c9 Add info icons for other overridden project prefs -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/geany/geany/pull/2316/files/509f716955a59b8bcc87e27207f8c98f07be9b15..32f99badc0db3a99285ad359d341aa86b98a22c9
Re: [Github-comments] [geany/geany] Enhancement - Vertical Editing Sequential Numbering (#2317)
To expand, basically its the Scintilla paste into rectangular selections default behaviour. Scintilla does have another option SCI_MULTI_PASTE to do it differently, but I'm not sure how much use it would be in this use-case. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2317#issuecomment-534907116
Re: [Github-comments] [geany/geany] Enhancement - Vertical Editing Sequential Numbering (#2317)
`Send selection to` pastes its result into the selection, thats why its the same issue. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2317#issuecomment-534904028
Re: [Github-comments] [geany/geany] Enhancement - Vertical Editing Sequential Numbering (#2317)
@elextr actually those issues are about pasting, not about Send selection to. Surely that's a separate issue? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2317#issuecomment-534901991
Re: [Github-comments] [geany/geany] Enhancement - Vertical Editing Sequential Numbering (#2317)
Ok, thanks Lex -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2317#issuecomment-534901363
Re: [Github-comments] [geany/geany] Enhancement - Vertical Editing Sequential Numbering (#2317)
> I've tried using the Send Selection To --> interface but it doesn't paste > back across the vertical selection. Yep thats known behaviour see also #625 #841 #850 #1083 several of which were opened by or commented on by one@AdamDanischewski (mentioning no names :) This whole thing will need to be examined if Geany ever moves to Scintilla 4 where rectangular selections have become multi-selections if I remember the Scintilla ML discussion correctly. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2317#issuecomment-534900845
Re: [Github-comments] [geany/geany] Enhancement - Vertical Editing Sequential Numbering (#2317)
> I've tried using the Send Selection To --> interface but it doesn't paste > back across the vertical selection. @AdamDanischewski if you have time, could you file this as a separate issue please? Note the manual calls 'vertical selection' rectangular selection. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2317#issuecomment-534886160
Re: [Github-comments] [geany/geany] Allow disabling use of GtkRecentManager (#2294)
> I would have no problem if Geany was adding nothing ;-) And of course its only a problem in Gnome, Cinnamon and its apps don't have a global recents list so no problem :) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2294#issuecomment-534885487
Re: [Github-comments] [geany/geany] Multi-line "Find in Files" searching (#2322)
> to implement the search in Geany and do away with grep That would basically have to reimplement grep. People can pass custom options. I don't think this is an effective use of time. > (which isn't available on windows by default, I think it's bundled with the installer. > and isn't neccessarily GNU grep on BSDs etc.). Is there a problem on BSD with any of the wrapped grep options? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2322#issuecomment-534884325
Re: [Github-comments] [geany/geany] Multi-line "Find in Files" searching (#2322)
I think you could already set pcregrep as the grep tool in preferences. Then in the other options entry you can add any necessary flags for multi-line matching. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2322#issuecomment-534882736
Re: [Github-comments] [geany/geany] Allow disabling use of GtkRecentManager (#2294)
> Geany should not be populating it for files opened whenever a project is > opened I haven't used the gnome feature, but maybe geany should only update Gtk recent items when a file is opened directly by the user or saved. So opening files from a session wouldn't add recent items. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2294#issuecomment-534879476
