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
... that way new users don't have to be told to uncomment the heading as well
as the setting they need, just the setting line.
And document this commenting behaviour in the manual.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on
@b4n now that you are returning `nullptr` from `pixels()` but you did not put a
check for that on the return value of every use of pixels() all you have done
is shift the problem. :stuck_out_tongue_winking_eye:
Now we can explain it, I suspect that it would be best to pass it to Neil to
> 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
> As I keep saying C++ is not C :grin:
I know, and I battle for avoiding this confusion. I just see once more that
C++ tries to be confusing for C programmers, reproducing syntax but with a
whole other lot of constraint that only apply in corner cases :grin:
Anyhow, a bad patch could be as
@elextr @b4n Correct me, yes I have now rebooted and everything works great,
thank you guys.
--
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/2502#issuecomment-739915354
@elextr Even by removing
both lines, does not show me the underscore ...
Can any of you send me your filetypes.common?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@Lo0is next time please paste to a pastebin and only paste a link here instead
of spamming every watcher of this repository with your whole file ... twice.
And to emphasise what @b4n is saying remove the `#~ ` from the `[styling]` line
and the `line_height=...` line.
--
You are receiving this
@b4n, yes, but std::vector is a library type, not a builtin, which keeps track
of its size and its capacity (which is why it is possible to insert the assert,
its has size to compare to, but in C since nothing saves the size of array you
malloced no automatic assert can be inserted in an index
@b4n
I also tried to put 1; 1; but it doesn't work anyway, I'll put the code back to
you after changing the values.
`#~ # For complete documentation of this file, please see Geany's main
documentation
#~ [styling]
#~ # use foreground;background;bold;italic or named_style,bold,italic
#~ # used
@Lo0is lines starting with `#` are comment lines, they are not used. You need
to comment-out line 2 so it reads `[styling]`, and the line that has
`line_height` so it reads `line_height=1;1;`.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or
This is my file, I hope it can help you to understand what is happening to me.
@elextr @b4n
`#~ # For complete documentation of this file, please see Geany's main
documentation
#~ [styling]
#~ # use foreground;background;bold;italic or named_style,bold,italic
#~ # used for filetype All/None
@elextr sure, but my point is that in C `[0]` does *not* dereference
anything, `pointer`could be anything so long as you d'ont
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@b4n, by default the C++ vector index is unchecked, but no index is legal on a
zero length vector, its UB, as the spec says about operator[] `Accessing a
nonexistent element through this operator is undefined behavior.`.
The assertions flag makes it checked, as the message you posted above says
https://github.com/openscad/openscad/issues/2965#issuecomment-500542956
--
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/1041#issuecomment-739878064
IIRC the other issue when `-D_GLIBCXX_ASSERTIONS` caused a crash, it was caused
by accessing `zero_length_vector[0]`. Let me try to find it.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@elextr for the moment your hint doesn't make much sense to me, you're just
point out that a 0×H image will have 0 bytes of data, which makes sense. I
don't see how it would account for accessing past the buffer, as the given size
is 0 in one direction. Well, of course the can be a bug some
@hroncok what that flag does is to make illegal indexing of vectors crash
rather than be ignored, so Fedora using it is why your Geany crashes but others
do not, but its not why the index was out of range in the first place.
--
You are receiving this because you are subscribed to this thread.
> Without testing further, my money would go on `-D_GLIBCXX_ASSERTIONS`.
I recall seeing this in other places as well, so I concur this is the flag.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@b4n
[hint](https://github.com/geany/geany-plugins/issues/1041#issuecomment-737609085)
--
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/1041#issuecomment-739857553
@elextr that's the next step, but I bet you can now debug it yourself as well
:wink: :wink: :wink:
I'll try and look at it maybe this evening if I find time.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@b4n neat, so now _why_ is the access to the vector out of range?
--
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/1041#issuecomment-739851825
> FTR the cflags in Fedora are:
> […]
> And ldflags:
Ah-ah! We got a winner. If I build Geany with those flags (minus the `-spec`
parameters that obviously don't work on my Debian):
```shell
$ export LDFLAGS="-Wl,-z,relro -Wl,--as-needed -Wl,-z,now"
$ export CFLAGS="-O2 -flto=auto
@b4n thats why I asked for it to be posted so we can check :)
See also my edit 6 comments above :)
--
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/2502#issuecomment-739806633
@Lo0is wait, I think I know the issue: is that setting properly in a
`[styling]` section? By default the section itself is commented (on line 2),
which then doesn't work.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@Lo0is post your filetypes.common in your favourite pastebin and post a link
here.
--
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/2502#issuecomment-739804217
@b4n sure, I've tried many combinations that goes beyond 1 but it doesn't give
me any kind of change
--
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/2502#issuecomment-739802114
@Lo0is did you try with bigger values than 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/geany/issues/2502#issuecomment-739795057
the solution did not help much, considering that I used another value but
nothing
--
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/2502#issuecomment-739753029
29 matches
Mail list logo
