The RPATH thing might still be needed when a non-system $PREFIX is used, also
there was some fiddling needed (see history above) because here libraries live
in `/lib/x86_64-linux-gnu` not in `/lib` and meson knows that, whereas the
autotools builder puts everything in `/lib` irrespective, so the
> Use the / path operator instead of join_paths() as well as for other paths
> where now they're just regular strings. Not sure what's idiomatic.
Probably should be https://mesonbuild.com/Syntax.html#string-path-building but
windows seems much less strict about the slash/backslash issue these da
Agree with @codebrainz suggested path above.
[STOP PRESS, the reason fnmatch and regex work on Linux (and presumably mac) is
that they don't get built, the meson configuration finds the system ones and
does not build the ctags internal copies]
--
You are receiving this because you are subscrib
I realize this is a more-or-less direct port from the Autotools build system,
but is it in the scope of this WIP PR to re-organize it to be more Meson-like,
or rather to get rid of Autotools-style/cruft?
A few things that stick out:
* Compiling all the things into helper static libs (Scintilla
I did try to tinker with it a bit, but not too much. I'll try other stuff next
time I boot into Windows partition.
--
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/pull/2761#issuecomment-8964120
@codebrainz if you want to test before @kugel- gets to it, in geany/meson.build
try making a copy of the `,include_directories: ...` parameter from lines 334
and 346 into the respective `static_library()` functions above those lines.
--
You are receiving this because you are subscribed to this
> I'm pretty sure Ninja is doing parallel compiles so the output is probably
> out of order.
Since ninja buffers output, the messages of different compile commands
shouldn't be mixed, but yes the order of the compiles may vary.
--
You are receiving this because you are subscribed to this thre
@codebrainz sorry I didn't look closely enough at it, saw the first error in
your build post was Scintilla and assumed it was all C++17 regex issues, but in
fact most of them are ctgas errors:
- missing which is the linux glob file match header, but its in
ctags/fnmatch
- at least some of the
> On mac, it's fixed now, but on some older version in mac...
I don't quite understand - you mean older version of macOS or older version of
geany? Older Geany versions won't get updated, it's just the latest release
which contains all the fixes.
--
You are receiving this because you are subsc
> @codebrainz not sure what the problem is, I would have thought g++ 10 would
> default to c++17, but maybe I'm wrong, does latest git Geany build with
> autotools on the same system?
I think the problem is with fnmatch/gnu_regex libraries which I believe are
special for Windows, and possibly j
I got it compiled on macOS with
```
meson _builddir -Dgtkdoc=false -Dcpp_std=c++17 && ninja -C _builddir
```
and Geany installs and runs fine.
The only problem I did run into during the compilation was inside
`doc/meson.build` where the `cp` commands take the `-u` parameter which is not
supporte
@eht16 commented on this pull request.
> @@ -335,6 +335,21 @@ void on_toolbutton_reload_clicked(GtkAction *action,
> gpointer user_data)
document_reload_prompt(doc, NULL);
}
+/* reload all files */
+void on_toolbutton_reload_all_clicked(GtkAction *action, gpointer user_data)
+{
+
@techee On mac, it's fixed now, but on some older version in mac, `geany xxx`
still start a new instance instead of reusing existing one, otherwise I won't
have created this issue back then.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or vie
Assuming this is a duplicate of #820, closing.
--
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/899#issuecomment-896309565
Closed #899.
--
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/899#event-5137749199
This is hopefully fixed. Closing.
--
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/738#issuecomment-896307834
Closed #738.
--
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/738#event-5137735669
I don't seem able to reproduce the problem. What exactly do you do? When I'm in
command mode, enter insert mode using `i`, type `g` and press ``, I get
back to the command mode.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHu
Doesn't Option+Shift plus arrows work? It at least works on my machine.
--
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-osx/issues/25#issuecomment-896289174
Closed #16.
--
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-osx/issues/16#event-5137490335
This is hopefully fixed in Geany 1.37. Closing.
--
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-osx/issues/16#issuecomment-896278547
@kuchaguangjie Yes, but your example doesn't open a separate Geany instance -
it opens the existing instance. The only case when a separate instance is
created is when you run geany without any arguments.
--
You are receiving this because you are subscribed to this thread.
Reply to this email d
@techee On unix-like desktop or mac, one use case is: Defining `alias
xxx="geany some_file"`, for some very common file, and whenever I want to open
it, I would simply type `xxx` in console, to open it, instead of find that
folder, and double click it.
I do this a lot on linux, with both geany
Ok, I'll wait. I very much appreciate the update, thank you.
--
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/pull/2830#issuecomment-896173619
@Davidy22 pushed 1 commit.
f96f2d9ce14737d75aa4aa5dd040a85628681a92 Combine confirmation dialogs
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://github.com/geany/geany/pull/2859/files/3cd9bcd577da1904e68e9f2ef20d22e449649eba..f96f2d9ce14737d75aa4
@Davidy22 commented on this pull request.
> @@ -335,6 +335,21 @@ void on_toolbutton_reload_clicked(GtkAction *action,
> gpointer user_data)
document_reload_prompt(doc, NULL);
}
+/* reload all files */
+void on_toolbutton_reload_all_clicked(GtkAction *action, gpointer user_data)
+{
+
@willbprog127 I created a new Geany binary with an updated theme that is based
on
https://github.com/vinceliuice/WhiteSur-gtk-theme
The installer is here if you want to give it a try
https://download.geany.org/snapshots/geany-1.38_test_osx.dmg
Not sure if it fixes the problem for you or not. I
> Geany 1.37 does different behaviour for me on macOS. If I invoke it with no
> file argument then it opens a brand new Geany process and Window. However, if
> I invoke it with a file argument then it will open the file in the original
> Geany process window. This behaviour is a little unusual :
Sometimes it is more convenient if the home button in the tree browser go to
the project base directory instead of the user home directory.
The pull request
https://github.com/geany/geany-plugins/pull/1095
add a combo box to the tree plugin preferences where the prefered home
directory (user h
@codebrainz not sure what the problem is, I would have thought g++ 10 would
default to c++17, but maybe I'm wrong, does latest git Geany build with
autotools on the same system? If it does build maybe the point I posted above
will fix it since it meant the standard wasn't explicit?
--
You are
Hmm, @kugel- `cpp_std` isn't a valid named parameter to `shared_library()` (see
the configure output @codebrainz posted), it should probably be in the
`cpp_args` if you want to apply it to only the Scintilla part of the build.
But personally I would add it in `add_project_options()` as per
htt
31 matches
Mail list logo
