Geany 1.28 Release (Windows and Linux) and Geany 1.29 and I think also Geany 1.27 and before
Lines that start with ';' are syntax highlighted as comment.
Lines that start with '#' are syntax highlighted as comment.
An entry "key=value" in a line starting with ';' is shown in the symbols list.
An entry "key=value" in a line starting with '#' is not shown in the symbols list.
I attached a small test file test.ini, but I had to rename it to test.ini.txt because github refused to upload test.ini
[test.ini.txt](https://github.com/geany/geany/files/464268/test.ini.txt)
--
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/1220
```C++
namespace ns {
class C {
void f( // when typing the ( the calltip says "ns::C::f (junk, rubbish)"
public:
C(junk, rubbish){}
~C(){}
};
};
```
Yep, takes the parameters for the constructor and it uses that as the prototype for the new function that doesn't exist yet.
And ... if there happen to be other functions named `f` the calltips will cycle through the prototypes of those functions and never come back to the erroneous one.
Seems like some extraneous function definition is being made for the calltip. But it never appears in the symbol list. Like as if something is scanning for the ) and using the parameter list immediately before it, ignoring the `public: C(`. But what, its not the parser because the symbol doesn't show in the sidebar?
--
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/1249
geany version - 1.29
Most of the function declarations in glibc header files are marked with __THROW.
Geany cannot identify or incorrectly identifies these functions.
(sample files /usr/include/pthread.h, /usr/include/unistd.h).
--
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/1314
I prefer that the terminal doesn't use bold fonts when printing characters with bold or highlight attribute since it's easier to my eyes.
This patch allows VTE to be configured that way through `vte_terminal_set_allow_bold()`.
Preview: http://i.imgur.com/KPZwPyi.png?1
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1132
-- Commit Summary --
* Allow VTE to be configured to not use bold fonts
-- File Changes --
M data/geany.glade (15)
M doc/geany.txt (3)
M src/keyfile.c (2)
M src/prefs.c (6)
M src/vte.c (3)
M src/vte.h (1)
-- Patch Links --
https://github.com/geany/geany/pull/1132.patchhttps://github.com/geany/geany/pull/1132.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/1132
```
(geany:3203): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
(geany:3203): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
(geany:3203): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
```
Suggestions where to look welcome.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/875
On Mac OS X , i can't use input chinese with Squirrel. When i input chinese in the editor, the editor still display english chars.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/920
This would allow us to force Geany to not open a new instance even
if no file arguments are passed in the command-line.
Some tweaks were also added so that the current instance window would
activate itself even if no new file arguments are specified whenever
this option is used.
This is useful if we want to make sure that we always only have a single instance. And also so we can have easy shortcuts to switch from a virtual terminal to the editor, like this function: `w() { geany -I "$@"; }`,
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1128
-- Commit Summary --
* Add '--no-new-instance' option.
-- File Changes --
M doc/geany.1.in (2)
M doc/geany.txt (3)
M src/libmain.c (32)
M src/main.h (2)
M src/socket.c (35)
M src/ui_utils.c (2)
-- Patch Links --
https://github.com/geany/geany/pull/1128.patchhttps://github.com/geany/geany/pull/1128.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/1128
Bash allows more characters besides `[[:alnum:]_]` when declaring
function names using the `function` keyword. It also does not require
having a pair of parentheses after the name. Some shells may actually
implement it differently but we don't have to be that strict since the
user explicitly specifies the `function` keyword anyway.
This update implements the ones described above, and also invalidates
function names that are completely made up of digits.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/662
-- Commit Summary --
* Enhance detection of sh functions
-- File Changes --
M tagmanager/ctags/sh.c (125)
-- Patch Links --
https://github.com/geany/geany/pull/662.patchhttps://github.com/geany/geany/pull/662.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/662
The ways on how a "folder name string" should be created and compared is divided in many parts of `get_doc_parent()` and the functions it call. One is from `get_folder_name()` itself, another is from `find_tree_iter_dir()` (`if (utils_str_equal(dir, ".")) dir = GEANY_STRING_UNTITLED;`), and another in the assignment of the item to `store_openfiles` (`DOCUMENTS_SHORTNAME, doc->file_name ? dirname : GEANY_STRING_UNTITLED`).
The ambiguity causes issues like having multiple parents in the Documents list that has the name `.` when the filename has a basename but not a directory name. This can be done by creating multiple new files with a template.
This patch is basically an overhaul to fix the ambiguity, and the issue is fixed along with it. If `get_folder_name()` is shared and used somewhere else besides `sidebar.c`, it would no longer require a wrapper just to make the returned string consistent.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1199
-- Commit Summary --
* Fix new files created with template not being placed in 'untitled' folder
* Place everything about creating document folder string in get_doc_folder()
-- File Changes --
M src/sidebar.c (128)
-- Patch Links --
https://github.com/geany/geany/pull/1199.patchhttps://github.com/geany/geany/pull/1199.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/1199
This is an alternative (which I find better) to https://github.com/geany/geany/pull/1191.
When cloning documents, a filename that's similar to the original - with a `.clone` extension appended to it, is given to the clone. The new filename is unique. It starts first with `filename.clone`. If the filename exists or is used by another document, a number is appended to it (e.g. `.clone1`), which increments until a unique filename is found.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1197
-- Commit Summary --
* Give '.cloneX' filenames to cloned documents
* Add documentation
* Use locale-encoded string when testing if file exists
-- File Changes --
M doc/geany.txt (6)
M src/document.c (46)
-- Patch Links --
https://github.com/geany/geany/pull/1197.patchhttps://github.com/geany/geany/pull/1197.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/1197
