The m4 files are downloaded from the Autoconf archive, they aren't shipped with
Autoconf where they would be copied from the system directory to the local m4
directory.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Yeah, as @elextr mentioned, the reason for the check is for an early failure
with a message explaining the compiler isn't supported.
Another way to do it would be to do a compile-test for only `std::string_view`
to also support non-C++17 compilers which might have already supported
@kugel- You're doing the work, so it's your call (and can be
discussed/refactored later). It just seems weird to have some stuff in subdirs
and most stuff in the main file, and then have separate build artifacts, but
not in own subdirs/subprojects; basically just seems a little inconsistent.
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
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:
> @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
Tried to test on Win10 with Msys2; seems to have some issues with the embedded
fnmatch/gnu_regex stuff.
* [Configure
Output](https://gist.github.com/codebrainz/0fcbfbfb9bd21d4c06ed542ff636ea46#file-configure)
* [Build
C++17 equivalent of previous Autoconf check that we got from the [Autoconf
Archive](https://www.gnu.org/software/autoconf-archive), which has since been
factored into two m4 files:
*
[ax_cxx_compile_stdcxx](https://www.gnu.org/software/autoconf-archive/ax_cxx_compile_stdcxx.html)
*
A nice sexy waitress waiter brings @eht16 a piece of sweet
chocolate, and a :+1:
--
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/www.geany.org/pull/30#issuecomment-863646409
I have not. I'll update here if I do. If anyone wants to work on it, ping me if
you need any assistance.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
After a little more research I think it might be possible to do it fully within
JS by loading the scroll position from the browser's localStorage (or maybe
just sessionStorage) when the DOM is finished loading and saving it before the
page is unloaded. If I can get that working, it should do
I do not, I just noticed that it was giving invalid/NULL and that I had a valid
document pointer already available. Probably one of the callbacks the plugin
uses gets triggered early before the document list is fully initialized or
something, but I didn't spend much time trying to understand
After a little bit of reading/experimenting, I think this is probably caused by
the Webkit2 no longer requiring a GtkScrolledWindow and handling scrolling on
its own in a separate process. Whenever the existing scrollbar adjustments are
read, the value is always zero, so the hack that was
For whatever reason, in some cases `document_get_current()` doesnt
return a valid document when it seems like it should, so when updating
the markdown preview from signals where the related GeanyDocument
is available, use that instead of calling `document_get_current()`.
In other cases, continue
Possibly related: #1095, #1076, #1278, #1534, #2660, #2652
--
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/2748#issuecomment-776058604
Might be a bug where the preview updates before the document is loaded and
doesn't update after it loaded. If you can reproduce, can you check what the
filetype shown in the statusbar says before you start editing?
:
> The main feature of this release is that I made a few things configurable
> (probably the most interesting one is the dark/light theme) using a config
> file which is created when you start Geany under
Closed #1059.
--
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/1059#event-4282565131
Duplicate of #1023 and fixed in #1053.
--
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/1059#issuecomment-772131923
> As a last resource (not as good) allow and document a "less hacky" way to
> change to dark mode...
If you set the `GTK_THEME` environment variable you should be able to switch to
the dark version, for example setting the environment variable to
`GTK_THEME=Mojave-light-solid:dark` should
Hi @subtra3t, this looks like a duplicate of #1902, #2408, #2472, #2572. It's a
good idea to search for existing same issues before posting a new one (I
searched "comma" to find those issues), and also to give your operating system
and version information.
Try out the solution in [this
> paging @codebrainz search services
https://groups.google.com/g/scintilla-interest/c/ma_3cmKAEVs/m/n61l9uT4BQAJ
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@codebrainz commented on this pull request.
> @@ -37,6 +37,7 @@ uninstall-local:
# manually install some files under another name
install-data-local:
+ sed -i '/Exec=/c\Exec=@bindir@/geany %F' @top_builddir@/geany.desktop
Ah ok. I was thinking it like the pkg-config file where do
@codebrainz commented on this pull request.
> @@ -37,6 +37,7 @@ uninstall-local:
# manually install some files under another name
install-data-local:
+ sed -i '/Exec=/c\Exec=@bindir@/geany %F' @top_builddir@/geany.desktop
Can't you just do this:
```diff
- Exec=geany %F
+
@eht16 Maybe before deleting we could [snarf it up in an
archiver](https://archive.vn/QPeDh) for posterity, including all the other SF
pages, and link them from somewhere on the main site?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view
I have no idea if other stuff (DEs, menu editors, etc.) purposefully use the
DE's `PATH` variable in all configurations, or whether it is common for DEs to
run under other than the currently logged in user, so not sure, no opinion.
--
You are receiving this because you are subscribed to this
Yeah, it doesn't recommend either way.
I'm not sure what the consequences of hard-coding an absolute path in practice
are - particularly in the case of multiple Geany installations - versus doing a
`PATH` lookup, so I do not have an opinion, other than that the unrelated
changes in this PR
> When I look at examples for creating .desktop files, it's recommended to use
> the full path to the binary.
Best source for info is [the
spec](https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html#exec-variables):
>> The executable program can either be
@TheDcoder FWIW, you can do this using just Geany:
https://www.geany.org/manual/current/#sending-text-through-custom-commands
--
You are receiving this because you are subscribed to this
I tried to fix this in d1a4dd15089551cd2eddcf9beb77ee9256f2d26f and I thought I
remember @b4n helping with this too, but I can't seem to find that discussion.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
It would have to use
[`GFileMonitor`](https://developer.gnome.org/gio/stable/GFileMonitor.html) on
the template file, seems perfectly do-able.
For the latter part, something like [Bootswatch](https://bootswatch.com/) would
probably do, and perhaps add a placeholder like `@@theme@@` to select
I believe this is a dupe of #1023
--
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/pull/1053#issuecomment-754972321
Closed #2717.
--
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/2717#event-4164421467
This is a duplicate of #905 even though they may have been requested for
different reasons. Please lets not scatter several discussions across duplicate
issues. #905 is older, has quite a few :+1: s and only has 6 comments including
one misunderstanding the request and one saying "patches
FWIW, the weirdness with new untitled files not opening sometimes is explained
in #2656.
I believe this issue is a duplicate of #905, and should be closed as such, with
further discussion on the already existing issue as to not bifurcate it.
--
You are receiving this because you are
Geany will only open additional unsaved new files if you've modified the
previous one, and will also only present the save dialog if you've modified the
new unsaved documents. The action of saving them to disk is what persists them.
> Is there a way to preserve those files in the editor without
For historical reasons, the default colour scheme is in
[filetypes.common](https://github.com/geany/geany/blob/d9f8cdbad58d09f0c18ca8acccb49209263018f0/data/filedefs/filetypes.common#L2).
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view
Link: https://sourceforge.net/p/scintilla/bugs/2226/
I'm not saying Zsh has it "wrong" per se, just that it seems to be the correct
behaviour for POSIX shells, and that in Geany, `*.zsh` files use the regular
[Shell
@codebrainz requested changes on this pull request.
What do you think?
> @@ -27,6 +27,10 @@ The basic features of Geany are:
- embedded terminal emulation
- extensibility through plugins
+Changelog
+-
+See the release notes on `the website
@RayAndrews56, @elextr is hoping you will open a bug on [the Scintilla bug
tracker](https://sourceforge.net/p/scintilla/bugs/) (there might already be one
for this, worth searching first), the project where the actual bug you're
experiencing would come from. If you're willing to do that, he's
@etkaar thanks, and sorry about all the confusion.
--
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/2697#issuecomment-751856162
This was finally fixed in master by 9f5b430458192388a7bf611943fc61b2a8b44246.
--
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/758#issuecomment-751855942
Closed #758.
--
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/758#event-4153011522
Merged #2697 into master.
--
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/2697#event-4153008432
Closed #2693 via #2697.
--
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/2693#event-4153008436
Slightly related: #2602
--
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/2713#issuecomment-751852035
Closing since same/similar info is available in numerous places.
--
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/2701#issuecomment-751850925
Closed #2701.
--
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/2701#event-4152977836
The one part of this multipart issue sounds like #15
--
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/21#issuecomment-751645249
@etkaar since this is already a duplicate of #2565, why not just force push to
the branch of this PR? This topic already has a number of duplicate issues and
PRs, no need to make more, IMO.
You can still keep this current work in a branch on your Github fork, Git lets
you branch off of
> I am concerned that certain terminal based UI applications may not properly
> work inside Geany.
IIRC Fish was using minimum 20 columns and 2 lines in its check, which seems
arbitrary, unless it's from POSIX standard? Moreover, at least here, Geany's
terminal has the correct output for `tput
Sounds like a problem with LibVTE and/or Fish (see [this
commit](https://github.com/fish-shell/fish-shell/issues/6980#issuecomment-625333808)),
but not Geany. Not sure it's even worth trying to workaround in Geany since
the message was removed in Fish and doesn't seem to affect any other
Real CSS has a property like this:
```css
filter: invert(1) hue-rotate(180deg);
```
But since GTK+ CSS is not real/complete CSS, I doubt it works.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #2647.
--
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/2647#event-4143563950
Duplicate of #1376, #1737, #2293, #2644, etc.
--
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/2647#issuecomment-750101493
Closed #2702.
--
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/2702#event-4143556521
`Tools` ⮞ `Configuration Files` ⮞ `geany.css`
Put this in it and save:
```css
.view {
background: black;
}
```
Message background color become full black when build is executed.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or
The `ChangeLog` is included in the official releases, it's generated from the
Git log during `make dist`.
If you don't want to compile Geany first, you can run `git log` from within the
Git source tree.
If you don't want to even check-out the Git source tree, you can [browse the
history
> If I understand your patch correct, it would change the default behaviour to
> do exactly that what my PL does, but per default and without a hidden
> preference.
Correct.
> ...but I think a hidden preference may be better than changing the default
> behaviour without allowing users to fall
Closed #2698.
--
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/2698#event-4137383980
@etkaar nice work.
> Should we then close this issue or link it to a specific "tutorial page"?
If you're willing, I would suggest to post a [HowTo on the
wiki](https://wiki.geany.org/howtos/start).
--
You are receiving this because you are subscribed to this thread.
Reply to this email
I thought due to [this
comment](https://github.com/geany/geany/pull/2695#issuecomment-748722240) the
request for an option was dropped? I think all this started over not closing
#2693 as a duplicate of #758 and not reading the discussion there.
Key points (duplicated across issues):
1) The
> We are very much trying to not dump things in various...
For what it's worth, this is not shared by _all_ core developers; personally I
feel that the Preferences dialog already has loads of options and that it's
better for preferences that are obscure or rarely used to be dumped into the
Add code block around above paste and removed `\` from in front of the comment
lines. Probably better to paste your exact file in between the `ini` code block
I added.
To me it looks like it's detecting as shell script (though can't be sure, as
@elextr said, your screenshots don't show the
This is the default behaviour so it should work automatically, [see
here](https://github.com/geany/geany/blob/d2740f21feb84b6f951398c6f683674b2b56bfed/data/filetype_extensions.conf#L67).
Documentation [is
here](https://www.geany.org/manual/current/index.html#filetype-extensions)
--
You are
FWIW, the Git installer for Windows asks you about how to deal with with line
endings (autocrlf) during setup and sets it globally. Maybe someone had that
configured and accidentally changed the line endings?
Agree. It seemed like a good idea, but is proving troublesome with people who
aren't familiar with GLib's keyfile format. At the very least the `[section]`
lines shouldn't be commented.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it
> But of course thats slower, whereas operator[] is as fast as C
Not true when distros enable debug assertions in release builds...
> reproducing syntax but with a whole other lot of constraint that only apply
> in corner cases
Kind of like making the bitwise shift operators sometimes mean
> So, the colored variant seems not relevant for the crash.
Agree, it seems unlikely that it's related to the font, but @hroncok does have
a different emoji font than Noto.
> Can I run it without make install? Do I need to do this with plugins and
> geany somehow combined?
You could configure
Here:
```bash
$ fc-match -s monospace | grep -i emoji
NotoColorEmoji.ttf: "Noto Color Emoji" "Regular"
```
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
> I don't have the "DejaVu Sans Mono Regular" font variant
Me either
> Also, my snowman is always in the uncolored variant
To copy into Geany, I had to "Edit" this issue description and copy/paste from
there (and then cancel the edit). I think you also need a fallback font that
provides it to
In my test I was using same font as @eht16 except size 10, but I believe
emojies fallback to some of the Noto* fonts, one for the black and white and a
different one for the colour emoji.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view
When I split a snowman I get this:
No crashes.
```
18:20:05: Geany INFO: Geany 1.38 (git >= d2740f21f), en_CA.UTF-8
18:20:05: Geany INFO: GTK 3.24.20, GLib
Closed #2680.
--
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/2680#event-4054622295
It works for me, though not for `flex-direction` specifically, since I tested
using the tags file linked from #572 and neither one includes `flex-direction`.
If I type `flex-`, it gives auto-complete list for `flex-align`, `flex-flow`,
`flex-line-pack`, etc.
Tested with 1.38.
What tags file
Related to/duplicate of #2484 et al.
Upstream bug: https://sourceforge.net/p/scintilla/bugs/1563/
--
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/2675#issuecomment-735023263
Closed #791.
--
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/791#event-4047544148
Closing as the issue seems to be resolved according to the comments. Feel free
to reopen if it is still an issue.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
I believe `string` is a library type, not a keyword.
You could add it to [the `primary`
key](https://github.com/geany/geany/blob/0a0b4b000cf18e837b921057a461ad05a08e41d3/data/filedefs/filetypes.d#L25).
Alternatively, you could add it to [the `types`
> Weird indeed… may be the same as #1022?
Was my first thought too.
--
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/1036#issuecomment-731484823
@vkireyeu good news!
If you are willing and able, it would be interesting to see if you experience
the same issue with [Scite](https://www.scintilla.org/SciTE.html) which is the
reference editor for the source code editing widget/component Geany uses
(Scintilla). If you experience the same
It's probably still Wayland, I don't think you can use per-app environment
variables if you're within Wayland. Try to log out and change the session to an
X-session instead of Wayland (gear icon -> 'GNOME on Xorg').
--
You are receiving this because you are subscribed to this thread.
Reply to
1) Result (default, not changed by me):
```bash
$ sudo env | grep PATH
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
```
2) That's what I did when testing.
I don't really want to change `PATH` and `ldconfig` stuff for root, if that's
what you're suggesting I do. But
For what it's worth, I just tested current `master` branch as well as this
branch (with a `make distclean` before each try) and they both worked. Ubuntu
20.04.1, all default build options.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view
@b4n I use Ubuntu 20.04 and can test. Can you describe the reproduction
procedure?
--
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/2661#issuecomment-728623583
> Btw, I tested successfully:
> * working directory with German umlaut, relative ASCII filename
> * working directory with German umlaut, relative filename with German
> umlaut
> * working directory with German umlaut, absolute path with German umlaut
> in directory, ASCII filename
>
I believe this is intentional and has been the case since very early, if not
the initial commit.
See the [code
here](https://github.com/geany/geany/blob/0a0b4b000cf18e837b921057a461ad05a08e41d3/src/document.c#L628);
when you open new untitled document and there's only one new/untitled document
Does it work when you choose to continue?
--
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/2655#issuecomment-725537662
Sounds like a duplicate of #618, #1508, #1708, #2081, etc.
Related: #1709
--
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/2654#issuecomment-724901820
> My solution would be to add comments to the CSS file so that the users of
> dark themes only have to uncomment to have a functional contrast.
I guess that still has the problem that we have no idea what GTK+ theme the
user will choose, so it's not really possible to pick properly contrasting
Sounds related to #1095.
--
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/2652#issuecomment-724370158
Seems to not be an issue on Linux.
References:
https://github.com/geany/geany/issues/2639#issuecomment-723489800
https://github.com/geany/geany/issues/2639#issuecomment-723494612
https://github.com/geany/geany-osx/issues/20
https://www.mail-archive.com/users@lists.geany.org/msg02989.html
--
You
Reopened #1023.
--
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/1023#event-3970334423
Then it is a bug.
--
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/1023#issuecomment-723514866
I have no idea about Macos, I was just linking your issue to the others about
the bad colours when dark mode/themes are used, sorry.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Sounds related to the recent https://github.com/geany/geany/issues/2644 and
similar previous issues.
--
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/2647#issuecomment-723495024
I noticed the slow startup on Windows since pre-releases of 1.37, I assumed it
was something with my computer/Windows. It's not a huge deal, but it certainly
seems slower than it ought to be.
Possibly related: https://github.com/geany/geany-osx/issues/20
Startup time in Ubuntu 20.04 seem
Could be a clash with another file including `stdbool.h` or also defining own
`bool` type.
IMO, it should either include `stdbool.h` and use the standard `bool` (alias of
`_Bool`) or else use `gboolean` that is already available via the `glib.h`
include.
@rezso if you want to test, try
All lines starting with `#` are comments, same as with Python. Try uncommenting
at least `[Python]` line and the line you added.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
1 - 100 of 2407 matches
Mail list logo
