# Description
If you add some macros into a type definition (ex. struct, enum, etc), the last token before the opening brace of the definition seems to be taken as the type name. I guess this is a bug in old `c.c` ctags parser.
# Example
```c
#define BLEH
struct foo BLEH { int _; };
```
Here, `BLEH` gets highlighted as the type name instead of `foo`.
# Use case
Using macros for things like GNU C's `__attribute__` extension.
# Version
I don't think version matters at all, but I'm using a fairly recent 1.32 build.
--
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/1654
One thing that drives me crazy is how when I have files associated with Geany, if I double click on them to open them, it will open the file in another Geany instance on *another* desktop instead of on the *current* desktop. This was one thing I took for granted when I was using gedit.
I have searched and found someone that suggested somehow using a unix socket file that is named based on the current desktop number, but I have not been successful in doing so. In fact, their solution seemed to lead to some loop that would keep spawning new Geany processes, bringing the OS to a near halt.
Can something like this be *baked in* to Geany so that no special setup or configuration is necessary? If there is a good reason not to, is there an official solution to this somewhere (that works)?
---
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/1025
Display the zoom level in percent in the document tab label.
If the zoom level is changed back to normal size then it will not be shown.
If a user just quickly wants to zoom in and back out then showing the zoom level helps to go back to the normal size without the need of using a keybinding or menu item. IMHO this makes zooming with the mouse wheel more comfortable. The zoom level is displayed in square brackets right beside the file name in a smaller, monospace font, e.g. ```main.c [110%]```.
This is comparable to Firefox which displays the zoom level beside the URL.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1697
-- Commit Summary --
* Show zoom level in document tab label.
-- File Changes --
M src/document.c (18)
M src/editor.c (1)
M src/sciwrappers.c (15)
M src/sciwrappers.h (2)
-- Patch Links --
https://github.com/geany/geany/pull/1697.patchhttps://github.com/geany/geany/pull/1697.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/1697
I have this on my mac for several days.
I uninstalled geany, tried 1.31 , searched throught the preference,
it's impossible to work with this because mouse if off by one title bar height.
--
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/1729
Recently I upgraded to Mac OS High Sierra and after the upgrade Geany will open a new instance when opening some xml's. The behaviour seems random, out of 10 XML files, 3 of them opens a new instance while the other 7 opens inside the already open instance.
I can't explain it and tried to search for the issue with no luck. Can I provide a log or any other information?
--
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/1619
Geany has some bug in full screen on OSX, like if you open the search window you can't close the full screen with the green button or the search window doesn't close anymore... and some crash when you try to save the project (always on full screen)
---
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/1046
Fixes issue #1000 . Geany now correctly autocompletes LaTeX macros.
The difference in behaviour can be illustrated with the following document:
````latex
\newcommand{\macroname}{}
% The following occurrences of \macro are now autocompleted to \macroname
\macro
\alpha\macro
% The following is no longer autocompleted to macroname
macro
% Example with @
\newcommand{\@anothermacro}{}
% Gets autocompleted
\@another
````
The tests were updated to accept this behaviour (since macro tags now start with `\`).
This also identifies macros defined with `\let`, `\newlength` and environments defined with `\renewenvironment`.
Finally, `@` can be used sometimes in a macro name and mostly any character can be used in a label. I added `:@` to wordchars so that they can be used in autocomplete.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1011
-- Commit Summary --
* '\' is included in macro tag.
* Updated copyright.
* Made indentation consistent with the rest of the project.
* Correctly separates LaTeX words.
* Environments can be defined with \renewenvironment as well.
* Correctly add macro tags.
* Macros can also be defined with \let
* Removed my copyright since I don't even know if I could add it.
* Updated tests to include \ in macros.
* Recognizes new lengths as macros.
-- File Changes --
M src/editor.c (31)
M tagmanager/ctags/latex.c (338)
M tests/ctags/3526726.tex.tags (4)
M tests/ctags/bug2886870.tex.tags (6)
M tests/ctags/intro_orig.tex.tags (6)
-- Patch Links --
https://github.com/geany/geany/pull/1011.patchhttps://github.com/geany/geany/pull/1011.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/1011
grep -nHIF -- $mail = new Mail(); (in directory: /drive2/www/html/opcsupportocmod/opcsupport_2031/)
/bin/grep: .idea: Is a directory
/bin/grep: admin: Is a directory
/bin/grep: catalog: Is a directory
/bin/grep: image: Is a directory
/bin/grep: system: Is a directory
Search failed.
--
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/593
I have filed a feature request for scintilla for the above, it would be great to have commonmark markdown syntax supported in this plugin as well since current markdown support is limited to basic markdown.
--
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/651
Hello, Everyone!
It would be great to have the [CommonMark](http://commonmark.org/) plugin.
The rationale:
> We propose a standard, unambiguous syntax specification for Markdown, along with a suite of comprehensive tests to validate Markdown implementations against this specification. We believe this is necessary, even essential, for the future of Markdown.
>
> That’s what we call CommonMark.
>
> — [CommonMark](http://commonmark.org/).
Best regards,
Sergey Brunov.
--
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/589