Greetings!
Using Geany 1.37 on macOS 1.14.6 (Mojave) Intel there is a problem with the default theme. When selecting text in the editor then right-clicking on this selected text, often the right-click menu will appear then disappear, and then an Undo has been performed. So far it appears to be random but frequent enough to cause problems and frustration.
As a workaround, I had to quit Geany, go into the `Resources`->`etc` folder in the app bundle and rename the `gtk-3.0` folder to `gtk-3.0~`. After restarting Geany, a slightly different theme is in use and the right-click menu behavior is now working properly.
It appears that the excessive animation of the Geany-bundled default theme is causing the problem. After renaming the `etc`->`gtk-3.0` folder, the GTK-macOS default theme seems to handle the right-click and menu navigation correctly.
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-osx/issues/24
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
It has been reported on the ML that the standard bundle works on Apple M1 silicon, @techee do you want to add a note in README to the effect that its reported to work but not tested by you (unless you do test on M1 :)
--
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-osx/issues/23
I didn't find such a feature request/enhancement, but if it was already requested (or feature already exists), feel free to close this issue.
It would be nice if Geany can highlight syntax for files without extensions. Let's say I open a new tab and copy/paste some PHP snippet to it. Some other editors will automatically highlight syntax as PHP in this tab if content starts with **<?php** (even if tan wasn't saved as some file with *.php extension extension).
Now, it's needed to save tab as a file with corresponding extension just to enable syntax highlight. Sometimes it's a pain in the a** because I often create a new tab, copy/paste some PHP snippet for temporary purposes, and close this tab in minutes. But if I need syntax highlight (which I need, of course), I have to manually save every tab as PHP file.
I realize some languages might not have starting words, but if it has, maybe Geany can auto-recognize and highlight syntax?
For example, these starting words surely indicate which language should be highlighted:
```
<?php
<html
<?xml
```
...and I'm sure the list will go on
--
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/1899
It would be very useful if markdown tag with **bold* or __italic__ changed color text. It doesn't work while other text editors 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/1497
Following the Mac OS Catalina update, Geany can't no more acces my "document" file : "Operation not permitted"
--
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/2397
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