1. Geany: V1.29
2. GTK+: V2.24.30;
3. My OS: Linux Mint 18.1 Serena Cinnamon Edition;
If putting `$\theta \in [0,2\pi)$` in my TEX file, all the code following it and before `\bibliographystyle{abbrv}` is not highlight. If I chang it to `$\theta \in$ $[0,2\pi)$`, it's good.
--
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/1403
When I type in Geany, the letters often take time to appear. For instance, let's say I type 6 characters in 2 seconds. Those 6 characters will appear one at a time, perhaps taking 2.5 or even 4 seconds to appear. This is a serious usability issue, and I have used Geany for a long time but never experienced it before.
This happens at varying degrees of severity on most files I work with. Will update if I discover anything new about the problem.
## Some info:
- OS: Opensuse Tumbleweed
- Geany: 0.32
- CPU: Intel Core i3-7100, Intel HD Graphics
- Desktop Environment: GNOME 3.26
- GTK theme: Adwaita
Let me know if you need anything more or have any suggestions! Even if you don't have suggestions or solutions, comment if you are having the same problem.
--
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/1787
20:49:15: Geany INFO : Geany 1.27 (git >= ad354b7), en_AU.UTF-8
20:49:15: Geany INFO : GTK 3.10.8, GLib 2.40.2
Ignore the commit, Geany Git is actually 27628c0 (I thought we fixed needing to re-configure to get the git version?)
After using Geany for a while sometimes when switching tabs only the line with the flashing caret displays the new file, then after a while some more displays etc.
If I move the cursor into the edit widget it all updates.
Its like Scintilla is not getting the correct triggers to cause full update.
This doesn't happen with all tabs, but the ones edited most.
@b4n any suggestions where to look?
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/807
This pull request updates the python parser to the uctags version. The most interesting things are from the following commit messages from the pull request:
tm_ctags update:
```
The new parser generates 2 tags for import statements like
from A import B
For A tag of the 'i' kind is generated, for B, tag of the kind 'x' is
generated. B includes A in its scope and when we omit generation of
'i', imports are printed in the sidebar with the full scope information
like
Imports
django.views.decorators.csrf.csrf_exempt
django.views.decorators.csrf.csrf_exempt2
django.views.decorators.http.require_POST
When we generate 'i' and map it to something (I used tm_tag_externvar_t
like for the imports themselves, there's nothing in the tag types
we have that would be a good semantic candidate here), the result
in the sidebar is
Imports
django.views.decorators.csrf
csrf_exempt
csrf_exempt2
django.views.decorators.http
require_POST
which is more readable IMO.
```
cython unit test updates:
```
I'm not sure if cython is officially supported by uctags and there's a
slight problem where the new parser omits space between type and
function argument name. E.g. it produces
method(self,inti)
instead of
method(self,int i)
```
Not sure if we should worry about the cython output much - we could also drop the cython unit tests if desired.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3031
-- Commit Summary --
* Use uctags version of python
* Update mappings in tm_parser.c
* Update python unit tests
* Update cython tests with a slightly buggy output
-- File Changes --
M ctags/Makefile.am (2)
D ctags/parsers/geany_python.c (862)
A ctags/parsers/python.c (1597)
M src/tagmanager/tm_parser.c (4)
M tests/ctags/cython_sample.pyx.tags (6)
M tests/ctags/cython_sample2.pyx.tags (2)
M tests/ctags/py_constructor_arglist.py.tags (33)
M tests/ctags/simple.py.tags (6)
M tests/ctags/tabindent.py.tags (2)
-- Patch Links --
https://github.com/geany/geany/pull/3031.patchhttps://github.com/geany/geany/pull/3031.diff
--
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/3031
# Abstract
When naming a variable something that isn't ASCII, but is still a valid Python3 identifier, the variable doesn't show up in the symbols list.
## Problem Info
### Test case:
```python
#!/usr/bin/env python3
# coding: utf-8
correct = bool()
对不对='对' if correct else '错'
```
Load up that file in Geany, then open the Symbols tab.
### What I expected to see
"correct" and "对不对" both show up in the Symbols list.
### What happened
Only "correct" shows up in the Symbols list.
## Extra info
1. <output>geany 1.27 (built on 2016-04-17 with GTK 2.24.30, GLib 2.48.0)<output>
2. OS: Ubuntu 16.04.1 LTS
--
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/1337
This code adds the name "HEADER_TEMPLATE" to the variables list in the side bar:
```
HEADER_TEMPLATE = '''
==============
|{:^15}| {}
==============
'''
```
However this code does not:
```
HEADER_TEMPLATE = '''\
==============
|{:^15}| {}
==============
'''
```
Running Linux Mint, Geany 1.29, Python mode.
Thanks for all your work! Keep it up!
--
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/1390
Using python, this code should only report 1 variable.
```
data = dict(
en = "beer",
de = "bier",
es = "cerveza"
)
```
But 4 variables are reported in the sidebar:
Thanks for all your work!
--
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/1417
When applying [PEP484](https://www.python.org/dev/peps/pep-0484/) (Type Hints) to variables, the list of "symbols" in the current file no longer displays the variables using type hints. The parser should be modified to recognize Python symbols using the format `VARIABLE: TYPE = VALUE`, rather than just `VARIABLE = VALUE`.
--
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/1943
Parsers for R and verilog from ctags are token-based instead of our line-based parsers and are definitely superior and all development should go towards these parsers.
The sh parser is not token based but the uctags version seems to handle more things.
Other 2 parsers which I think we should eventually adopt are VHDL and tex parsers (both are token-based) - they generate a slightly different set of tags and tag mappings should be adopted to those for the sidebar so I skipped them for now.
Finally, I tried also switching to uctags `c.c` for java, D and C# but our c.c seems to be actually better there.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3035
-- Commit Summary --
* Use uctags R parser
* Update R kind mappings
* Use uctags parser for sh
* Update mappings for sh parser
* Use uctags verilog parser
* Update mappings for verilog parser
* Update verilog unit tests
* Add R and Verilog to languages reporting context
-- File Changes --
M ctags/Makefile.am (7)
D ctags/parsers/geany_r.c (177)
D ctags/parsers/geany_sh.c (110)
D ctags/parsers/geany_verilog.c (332)
A ctags/parsers/r.c (1470)
A ctags/parsers/r.h (111)
A ctags/parsers/sh.c (490)
A ctags/parsers/verilog.c (2024)
M src/tagmanager/tm_parser.c (14)
M tests/ctags/bug1111214-j-chan.v.tags (4)
M tests/ctags/traffic_signal.v.tags (24)
-- Patch Links --
https://github.com/geany/geany/pull/3035.patchhttps://github.com/geany/geany/pull/3035.diff
--
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/3035
){kind=link}