It is possible to define variables such as
```
struct {/* someting */} a, b;
```
In this case, we need to change the 'var_type' to correspond to the
renamed anonymous struct.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3196
-- Commit Summary --
* Fix renaming of variables with anonymous type
-- File Changes --
M src/tagmanager/tm_ctags.c (20)
-- Patch Links --
https://github.com/geany/geany/pull/3196.patchhttps://github.com/geany/geany/pull/3196.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3196
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3196(a)github.com>
To correctly rename anonymous tags the tag renaming function had to be updated for a special case in Fortran - see the commit for more details.
I also updated 2 unit tests which (I believe) contained invalid Fortran code the new parser didn't handle.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3160
-- Commit Summary --
* Fix anonymous tag renaming for Fortran structures
* Use the upstream Fortran parser
* Update unit tests
-- File Changes --
M ctags/Makefile.am (2)
R ctags/parsers/fortran.c (744)
M meson.build (2)
M src/filetypes.c (2)
M src/tagmanager/tm_ctags.c (16)
M src/tagmanager/tm_parser.c (22)
M src/tagmanager/tm_parser.h (2)
M src/tagmanager/tm_parsers.h (2)
M tests/ctags/bug565813.f90.tags (4)
M tests/ctags/bug670433.f90.tags (2)
M tests/ctags/bug726712.f90.tags (6)
M tests/ctags/enum.f90.tags (26)
M tests/ctags/forall_module.f90.tags (2)
M tests/ctags/fortran_associate.f90.tags (2)
M tests/ctags/members.f90 (4)
M tests/ctags/members.f90.tags (2)
M tests/ctags/numlib.f90.tags (1)
M tests/ctags/procedure_pointer_module.f90.tags (2)
M tests/ctags/qualified_types.f90 (4)
M tests/ctags/square_parens.f90.tags (2)
M tests/ctags/stdcall.f.tags (4)
M tests/ctags/structure.f.tags (2)
-- Patch Links --
https://github.com/geany/geany/pull/3160.patchhttps://github.com/geany/geany/pull/3160.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3160
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3160(a)github.com>
(This is an attempt to address various comments from #3018 - check this pull request for more details.)
Improve user experience when creating new projects
At the moment, when creating a project, the user is greeted with the
dialog containing:
1. Name
2. Filename
3. Base path
The user is expected to type the name of the project into (1), and then,
Geany tries to guess the base path and file name. The guess simply takes
the project directory specified in settings and appends the name. When the
project is located anywhere else than in the projects directory,
the guessed values are wrong and have to be entered manually which is
quite annoying. In addition, the dialog doesn't make it clear that the
user should start with (1), when he starts with (2) or (3), he has to
fill in all 3 values manually.
This patch adds another method of project creation which is more
suitable for creating projects from existing directory with source
files. There's a new "Project->New from Folder..." option that in
the first step asks user to provide the base path and based on this
path fills in the entries in the New Project dialog.
With this approach, Project->New from Folder...:
a. First pops up a open directory dialog to specify base path
b. After that, opens the (currently used) New Project dialog which
is pre-filled in the following way:
1. Name: The last directory in base_path
2. Filename: depending on "store project file inside the project base
directory" settings either in base_path/(1).geany or projects_dir/(1).geany
3. Base path: path specified in (a)
This way, in most cases, the user will only have to select the base
directory in the first step and use the pre-filled values without
any modification no matter whether the project is stored in the projects
directory or not.
After this patch, there will be 2 different ways to create projects:
1. Project->New - more suitable for creating empty projects from scratch
inside the "projects" directory
2. Project->New from Folder - more suitable for creating projects from
existing sources
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3042
-- Commit Summary --
* Improve user experience when creating new projects
* Add keybindings for "Project->New from Folder"
* Store project files in base directory by default
* Make the New Project dialog a little wider
-- File Changes --
M data/geany.glade (17)
M src/callbacks.c (8)
M src/callbacks.h (2)
M src/keybindings.c (5)
M src/keybindings.h (2)
M src/keyfile.c (2)
M src/plugindata.h (2)
M src/project.c (77)
M src/project.h (2)
M src/ui_utils.c (15)
M src/ui_utils.h (2)
-- Patch Links --
https://github.com/geany/geany/pull/3042.patchhttps://github.com/geany/geany/pull/3042.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/3042
When I open a typescript file (.ts), I can't navigate between symbols because geany doesn't find any symbol.
However, in a javascript file (.js) I can't navigate between symbols with no problem, for example, classes, methods, constructor, 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/2442
Alternatively, there's also EmacsLisp parser (also inside lisp.c) which
could be used instead.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3164
-- Commit Summary --
* Add lisp ctags parser
-- File Changes --
M ctags/Makefile.am (1)
A ctags/parsers/lisp.c (389)
M meson.build (1)
M src/filetypes.c (2)
M src/tagmanager/tm_parser.c (15)
M src/tagmanager/tm_parser.h (1)
M src/tagmanager/tm_parsers.h (3)
M tests/ctags/Makefile.am (1)
A tests/ctags/simple.lisp (17)
A tests/ctags/simple.lisp.tags (9)
M tests/meson.build (1)
-- Patch Links --
https://github.com/geany/geany/pull/3164.patchhttps://github.com/geany/geany/pull/3164.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3164
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3164(a)github.com>
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3162
-- Commit Summary --
* Add Clojure ctags parser
-- File Changes --
M ctags/Makefile.am (1)
A ctags/parsers/clojure.c (195)
M data/filedefs/filetypes.Clojure.conf (1)
M meson.build (1)
M src/tagmanager/tm_parser.c (11)
M src/tagmanager/tm_parser.h (1)
M src/tagmanager/tm_parsers.h (3)
M tests/ctags/Makefile.am (1)
A tests/ctags/simple.clj (15)
A tests/ctags/simple.clj.tags (7)
M tests/meson.build (1)
-- Patch Links --
https://github.com/geany/geany/pull/3162.patchhttps://github.com/geany/geany/pull/3162.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3162
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3162(a)github.com>
The new parser reports scope so update the corresponding functions.
In addition this patch adds new root "Part" for reporting parts and
adds a separate "Bibitem" root (bibitem and label items used to be
reported together which I think is a bit confusing).
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3159
-- Commit Summary --
* Update to the upstream latex parser
-- File Changes --
M ctags/Makefile.am (3)
D ctags/parsers/geany_tex.c (242)
A ctags/parsers/tex.c (1253)
A ctags/parsers/tex.h (114)
M meson.build (3)
M src/tagmanager/tm_parser.c (29)
M tests/ctags/3526726.tex.tags (266)
M tests/ctags/bug2886870.tex.tags (19)
M tests/ctags/intro.tex.tags (18)
M tests/ctags/intro_orig.tex.tags (17)
-- Patch Links --
https://github.com/geany/geany/pull/3159.patchhttps://github.com/geany/geany/pull/3159.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3159
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3159(a)github.com>
The test.vhd file is more than 8000 LOCs, it seems to be multiple
concatenated VHDL sources and because of the large amount of tags,
it's hard to see the changes.
The new parser supports scope reporting so update tm_parser_has_full_scope().
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3158
-- Commit Summary --
* Add "el" as "Lisp" filetyp extension
* Added semicolon
* Add VHDL unit tests from uctags and remove the giant test.vhd
* Use the upstream VHDL parser
-- File Changes --
M ctags/Makefile.am (2)
D ctags/parsers/geany_vhdl.c (289)
A ctags/parsers/vhdl.c (1083)
M data/filetype_extensions.conf (2)
M meson.build (2)
M src/tagmanager/tm_parser.c (36)
M tests/ctags/Makefile.am (6)
M tests/ctags/bug2374109.vhd.tags (2)
D tests/ctags/test.vhd (8174)
D tests/ctags/test.vhd.tags (358)
A tests/ctags/vhdl-component.vhd (54)
A tests/ctags/vhdl-component.vhd.tags (9)
A tests/ctags/vhdl-local.vhd (203)
A tests/ctags/vhdl-local.vhd.tags (34)
A tests/ctags/vhdl-port.vhd (5)
A tests/ctags/vhdl-port.vhd.tags (7)
A tests/ctags/vhdl-process.vhd (51)
A tests/ctags/vhdl-process.vhd.tags (13)
A tests/ctags/vhdl-type.vhd (325)
A tests/ctags/vhdl-type.vhd.tags (121)
M tests/meson.build (6)
-- Patch Links --
https://github.com/geany/geany/pull/3158.patchhttps://github.com/geany/geany/pull/3158.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3158
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3158(a)github.com>
The TCL parser is split into three parts:
tcl - for parsing pure tcl code
tcloo - for parsing tcloo OO extension of tcl
itcl - for parsing itcl OO extension of tcl
TCLOO and ITCL parsers run the TCL parser as a subparser but it isn't
possible to combine all three parsers at the same time. Since TCLOO
is the "modern" (but 10 years old) OO extension, it seems to be a better
choice for Geany (if needed, a new filetype could be introduced for
ITCL).
Since it's run as a subparser, we need to introduce also a subparser
tag type mapping for TCL (types are mapped to the same values here
because they don't conflict with the TCLOO types).
Also, the new parser reports full scope information so take care of that.
In addition, scope by the TCL parser is prefixed by :: which we need
to strip because the TM doesn't expect scope in this format.
Update the unit test based on several uctags unit tests to cover the
tags we generate with this parser.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3157
-- Commit Summary --
* Use the upstream TCL parser
-- File Changes --
M ctags/Makefile.am (4)
D ctags/parsers/geany_tcl.c (145)
A ctags/parsers/tcl.c (716)
A ctags/parsers/tcl.h (51)
A ctags/parsers/tcloo.c (201)
M meson.build (4)
M src/filetypes.c (2)
M src/tagmanager/tm_parser.c (31)
M src/tagmanager/tm_parser.h (1)
M src/tagmanager/tm_parsers.h (3)
M tests/ctags/simple.tcl (59)
M tests/ctags/simple.tcl.tags (19)
-- Patch Links --
https://github.com/geany/geany/pull/3157.patchhttps://github.com/geany/geany/pull/3157.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3157
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3157(a)github.com>