> 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:
https://github.com/geany/geany/issues/2731#issuecomment-7641605
Closed #2731.
--
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/2731#event-4230823664
ummno w correctly copy cat adn understand.. puff so i cant backport geany 1.33
to olders versions of my production environment devbelopers.. puff i already
noted you guys were using the LongTerm3 brand for a while .. so i cant make
anything .. so i will try to backport the 1.26 version or less,
The errors posted in the OP (assuming Scintilla 3.7.5 or earlier, the line is
blank in later versions) do indeed look like a known bug in early C++11
compilers that didn't detect the return value was an rvalue and required
`std::move` on them. Of course then once that was fixed, later compilers
> But if we accidentally started to depend on C++14, we probably should write
> this down
Not knowingly, Longterm3 branch claims "avoiding C++14" but Mitchell could have
made a mistake, but since he has retired the branch its not going to be fixed
if something did sneak in.
@b4n to explain, th
> it seems related to this commit
> [170ebf6](https://github.com/geany/geany/commit/170ebf610f33ac414799f1a841ae01c1e058d567)
> so i'll try to investigate a little but seems i'll need more help
I hardly think this commits has anything to do with your problems, and I don't
see any reference to t
> And a rant of my own if I may, I am tired of people demanding that others
> invest the effort to support their particular configuration with no
> contribution of their own. Even to find the cause and possible workarounds
> takes effort that somebody has to provide. As I said above, even distro
> > i'm asking about any trick or workaround puff
>
> * Build a new enough GCC for yourself
> * Adjust Scintilla's sources not to require features not in GCC 4.8
> * If it's that simple, figure out a set of GCC 4.8 options that make it work
> (I'm afraid there won't be any)
> * Convince Scintilla
it seems is related to this commit: 170ebf610f33ac414799f1a841ae01c1e058d567 in
fact the error is produced in that line and inherits
--
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/2731
> Do you know if it would be always computed or only when the user includes %u
> in their statusbar template.
This is a question for the new issue you were asked to create on the Geany repo
for that.
Keep this issue for the plugin for character names, and that issue on Geany
itself for the sta
> A well written pull request that added say %u to the status bar template
> values to show the code point in the line would probably be accepted,
Unfortunately, I only know little bit of JavaScript. :-/
> just needs care to minimise the cost as it would have to be counted each
> update, and s
> Build a new enough GCC for yourself
Its probably not even necessary to do that, for example Ubuntu 16.04 (which has
4.8 as the default compiler) has 4.9 and 5.4 in the repos ready to install.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly o
> i'm asking about any trick or workaround puff
* Build a new enough GCC for yourself
* Adjust Scintilla's sources not to require features not in GCC 4.8
* If it's that simple, figure out a set of GCC 4.8 options that make it work
(I'm afraid there won't be any)
* Convince Scintilla's authors not
Yes the compiler requirement is driven by Scintilla, but thats a separate
project and can make its own decisions, and Geany is only one of the users of
that software. Whilst a branch compatible with C++11 has been maintained until
recently, because the requirement for C++17 the day the standard
> [Edit: assuming you are compiling Geany 1.37 a fully working C++11 compiler
> is needed, and as shown GCC 4.8 isn't that, 1.38 will probably need a c++17
> compiler which I think is at least GCC 7]
umm ok so @elextr geany 1.30+ will need moderns compilers .. pufff please is
there any workaro
Since Geany does not have a written set of rules for github usage it can be
difficult for new contributors. Geany is a totally volunteer project, people
do what they _want_ to do if they have time and ability. There isn't a cadre
of paid programmers who are looking for the next thing to do, so
Understood.
It's just a thing I use in GitHub, usually. :)
Can come in handy in some projects.
--
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/1599#issuecomment-763580960
@jesus2099 stop giving bad advice, this project does not run on the number of
+1s
--
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/1599#issuecomment-763577997
@jesus2099 no point, github makes an entry in the original noting the duplicate.
--
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/2202#issuecomment-763577550
@lep42, this looks like a duplicate of #745.
If so, it might be closed.
But make sure to upvote the original ticket to show the demand:
1. Go to #745
2. Click the smiley button (top right) and
3. Click 👍
--
You are receiving this because you are subscribed to this thread.
Reply to this email di
@wrgcpp, when your ticket is closed as duplicate, please upvote the original
ticket to show the demand:
1. Go to #745
2. Click the smiley button (top right) and
3. Click 👍
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
h
Sorry, I was editing my big post above when you replied.
No need to elaborate on the tabs vs spaces here.
IMO it's using space as tabulation that is ugly workaround bringing too many
specific work-arounds (like this virtual column position: 1 character but 4
characters).
This ticket is already
> Unicode code point sounds like a genuine feature of Geany, more than a plugin
Correct as the edit above said and on geany/geany#2733
--
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/is
I would suggest you create a new issue requesting the status bar count, _if_
such an issue doesn't already exist, as I said elsewhere, it seems reasonable
if it can be done sufficiently efficiently. But nobody will find the
suggestion buried in here.
Yes tab indents are an idea from the 1970s
Thanks for the correct **Unicode code point**. :)
It's all English and I don't master it.
- **Unicode code point** sounds like a genuine feature of Geany, more than a
plugin
- **Unicode character name** would be a nice to have plugin: personally I would
not miss this much if I had the above alre
I assume that by your loose use of "character" you actually mean Unicode code
point. When we are talking about these things its important to be precise, as
was pointed out on #2733.
A well written pull request that added say %u to the status bar template values
to show the code point in the li
Indeed for the **character count** used as we can see with tabs and combining
characters.
And I do think it's better to master what your code contains, by showing
character count, rather than having the virtual column number we have.
You're right that eslint should call this number, **Char** ins
It would be nice that the [statusbar
template](https://www.geany.org/manual/current/index.html#statusbar-templates)
could get new placeholders for **character position** (see #2733) and
**character code and/or name**:
 in
the `foo` and see what the "column" of the bar error says, although the `o
Umlaut` shows as one its actually `o` and a `Umlaut` combining c
Yes adding it to the goto line dialog like that would be possible, just needs
somebody to do it.
--
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/869#issuecomment-763490785
In the file with `Tab a` go to the next line and type 5 `a`s , the last `a`
lines up with the `a` in the line above, so clearly the `a` in the line above
is in column 5.
You appear to have confused character count and column count, a column is a
vertical strip of screen, a character is an entit
For instance, in EmEditor, the command Jump to line… was renamed long time ago
to Jump… (Ctrl+G).
The column fields defaults to 1, to mimic the Jump to line behaviour:
So, if
Therefore, eslint error messages (correct) lead to wrong column.
--
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/2733#issuecomment-763438573
Open a document (JavaScript) that only contains a Tab followed by any character.
Status bar settings should use `%C` to display column position (if your setting
is `%c`, subtract 1 to all my examples).
→a
(where the → character represents the Tab character)
- When you press Ctrl+Home, colum
Its not that there is no understanding of the potential benefits, but ...
Its not so simple as saying it, there have been several attempts to make it
happen.
But they require a _lot_ of work because lots of the existing code simply
wasn't written to allow for more than one pane (which is why
Aha. Would reduce confusion and improve productivity, if both panes had the
same functionality, though. Thanks.
--
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/2732#issuecomment-76336353
If this is in the second pane, then its not unexpected, the second pane has
limited functionality and is best considered a read-only pane.
Also split-window is in the geany repo, not geany-plugins, moved.
--
You are receiving this because you are subscribed to this thread.
Reply to this email d
When using the splitwindow plugin auto-indentation for a new line is not
applied (when activated in settings > editor > indentation), instead the cursor
is set to the first position of the new line. This is valid for the lower resp.
right panel of the split window. In the upper resp. left panel
When using the splitwindow plugin auto-indentation for a new line is not
applied (when activated in settings > editor > indentation), instead the cursor
is set to the first position of the new line. This is valid for the lower resp.
right panel of the split window. In the upper resp. left panel
Hi @abdulbadii
It sounds like you would like to change the "find" options during a "find" of
the same text. Meaning:
Start search for "foo" in a document ->After first instance is found, find next
(Ctrl G) but change one of the options, such as "Case sensitive"
I was just trying that out... O
Closed #2728.
--
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/2728#event-4225962841
> This has a few issues IMO:
>
> * The way you modify the file _changes the whole line_, meaning that if
> that rule and the source file are not in sync, it's super hard to diagnose
> weird content in the installed file (as it ignores the content of the source
> file).
>
> * I don't li
42 matches
Mail list logo
