Purple editors pencil has been deployed :-)
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3592#issuecomment-1760568000
You are receiving this because you are subscribed to this thread.
Message ID:
@elextr requested changes on this pull request.
A couple of changes.
> @@ -1785,6 +1786,25 @@ This works basically the same as on other platforms::
"c:\program files\geany\bin\geany" -g c:\mytags.php.tags
c:\code\somefile.php
+Generating tags files using ctags
> I don't see how it should get better by postponing to 2.1.
The obligatory last minute Windows change? ;-P
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3063#issuecomment-1760552595
You are receiving this because you are subscribed to this thread.
When given, it specifies the kind introducing the scope information. May be
another way to speed up parsing of scope in addition to the sZ field.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3598
You are receiving this because you are subscribed
@elextr Would you mind having a look at the update of geany.txt I made in
https://github.com/geany/geany/pull/3049 if it looks alright to you?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3592#issuecomment-1760450881
You are receiving this because
@techee pushed 1 commit.
bb64384a6af2631ff6f4168118ff27e0dff1c4b5 Update geany.txt with ctags usage for
generating tag files
--
View it on GitHub:
https://github.com/geany/geany/pull/3049/files/d945009828e3c36b366a42448b009ea66f784090..bb64384a6af2631ff6f4168118ff27e0dff1c4b5
You are
> I don't see how it should get better by postponing to 2.1.
OK, I just thought it kind of died because of different opinions but I'm all
for it myself.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3063#issuecomment-1760445091
You are receiving
Merged #1278 into master.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1278#event-10637128409
You are receiving this because you are subscribed to this thread.
Message ID:
I don't see how it should get better by postponing to 2.1.
To me, switching to @techee's version of the Prof-Gnome theme is a big
improvement over the default theme. In the mean time, the website FAQ explains
how to change the GTK theme on Windows, so users who do not like it, can change
it
> At least we can easily change the PHP tags generation script when needed.
But we still need to support user's tag files possibly generated by older ctags
versions so it should stay there for some time even if we update the php parser.
--
Reply to this email directly or view it on GitHub:
@techee pushed 3 commits.
e1ae976a7284d59f24b387825e967a2e6794a330 Add ctags 'readtags' library to allow
us parse ctags files
d364c30e7973ceaf387f8c64211d3980a462f90b Fix compilation when TM_DEBUG is
defined
d945009828e3c36b366a42448b009ea66f784090 Use the readtags library to parse
ctags
> > We'll still need the "unknown" check to support older ctags binaries
> > unfortunately.
At least we can easily change the PHP tags generation script when needed.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3049#issuecomment-1760373686
You are
Didn't you like the second commit's message? :D
Done and thanks for review.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3594#issuecomment-1760362118
You are receiving this because you are subscribed to this thread.
Message ID:
Merged #3594 into master.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3594#event-10636857656
You are receiving this because you are subscribed to this thread.
Message ID:
@eht16 commented on this pull request.
On doc/images/build_menu_commands_dialog.png:
It won't get better. No idea what I'm doing wrong.
I managed to scale the display to 60% (after enabling some experimental feature
in mutter via gsettings and then changing the scale in some XML file) but it
@b4n commented on this pull request.
> + if (sci_get_line_from_position(sci, pos_next) == line)
+ char_width = SSM(sci, SCI_POINTXFROMPOSITION, 0, pos_next) - x;
I guess I feel like the popup should be under the letter the caret is at (not
sure what are the real differences
@b4n pushed 1 commit.
3498fe12a3be953511b810e568991e4149f2613a Fix popup position on a wrapping
corner case
--
View it on GitHub:
https://github.com/geany/geany/pull/3316/files/4a2999c18e2db59bb40b90ad6453732a2596a316..3498fe12a3be953511b810e568991e4149f2613a
You are receiving this because
Yeah, I'm afraid it's time to create the 2.1 milestone ;-).
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3063#issuecomment-1760342824
You are receiving this because you are subscribed to this thread.
Message ID:
@eht16 @techee are we really gonna do something about this for next release, or
is this lingering from release to release? :slightly_smiling_face:
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3063#issuecomment-1760315004
You are receiving this
Submitted my version as #3597
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3578#issuecomment-1760302273
You are receiving this because you are subscribed to this thread.
Message ID:
Fixes #3424.
This is my alternate proposal over #3578, as suggested there. If nobody
complains, Ill use that -- but even better, somebody else could test and
merge :wink:
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3597
-- Commit
Merged #3591 into master.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3591#event-10636308048
You are receiving this because you are subscribed to this thread.
Message ID:
@b4n approved this pull request.
LGTM, but you could squash the second commit into the first :wink:
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3594#pullrequestreview-1675065827
You are receiving this because you are subscribed to this thread.
> We'll still need the "unknown" check to support older ctags binaries
> unfortunately.
Sure, but it'll still make it more coherent. Unless we fear it'd break
compatibility at some level…
> OK to rebase this branch on top of master so it can be more easily tested
> with the php and py tag
> But if uctags still generates the parent_kind:A::B::C form the problem will
> still apply in the case of ctags generated files without sZ so needs to still
> be able to read those files. And document the ctags option as recommended
> somewhere.
The documentation is a good point, I'll write
> Good catch. Maybe it'd be worth submitting an update to that parser to be
> more in line with the convention as well.
We'll still need the "unknown" check to support older ctags binaries
unfortunately.
OK to rebase this branch on top of master so it can be more easily tested with
the php
@zen0bit commented on this pull request.
> msgid "_Backspace key unindents"
-msgstr "Klávesa tabelátor odsazuje"
+msgstr "_Klávesa tabelátor odsazuje"
done
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3595#discussion_r1357170933
You are receiving
@zen0bit pushed 1 commit.
b0f2d909332fdbc447003a349a40a0de460b1d6b update czech translation
--
View it on GitHub:
https://github.com/geany/geany/pull/3595/files/0821da0a2600de5e9876dfd89777205e7e4fd40a..b0f2d909332fdbc447003a349a40a0de460b1d6b
You are receiving this because you are subscribed
After updating to Scintilla 5.3.7 the Scintilla popup with the diff against git
shows the wrong number.
It seems that gtk_widget_set_size_request() scrolls Scintilla view so despite
it was set previously, it isnt set correctly after this call and has to be
re-set.
Note that the call to
@andrej-herceg commented on this pull request.
> msgid "_Backspace key unindents"
-msgstr "Klávesa tabelátor odsazuje"
+msgstr "_Klávesa tabelátor odsazuje"
backspace here?
--
Reply to this email directly or view it on GitHub:
> > I wrote most of it, it ought to be perfect
>
> Oh, I'm syncing it in the wrong direction - I should have updated ctags with
> your code :-).
Meh, I also wrote some of that one, so either way works :grinning:
> I discovered one more problem - all parsers use `typeref:typename` but I just
Many thanks elextr. The auto-close plugin adds semicolon while typing a know
function, therefore it should be enough in most circumstances. I will implement
your suggestion anyway because I am wondering if this plugin is not interfering
with Firefox somehow. I have some keyboards issue in
There is no built-in "add semicolon at EOL" action, so you can't just set a
keybinding.
You might be able to define a macro with suitable keystrokes using the
geanymacro plugin and assign that a keybinding.
--
Reply to this email directly or view it on GitHub:
33 matches
Mail list logo
