Geany improved a lot in protecting users from unintentional file overwriting when a file was changed outside the editor. However, Geany is missing one step. After the file content was changed, Geany informs users, offering one of three options: discard changes and reload the buffet content, discard the file content and overwrite from the buffet, or Cancel (means do nothing). Often users don't want to discard anything and select Cancel. However, later, when we intend to save, Geany doesn't remind anymore that the buffer content was older than on disk. There are many reasons why text editors should always confirm with users before overwriting the file. That is the standard behavior of the most of editors, such as vim, gedit, emacs, and much more. Geany should match other editors in this aspect, too.
--
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/1885
Following code makes cppcheck (the current revision 703e0a01534b14e6d8ebbefe59ea6b9ad95f29e2 from the master branch) report an incorrect error.
```
template <typename T>
using foo = enable_if_t<is_same<T, int>() && sizeof(int) == 4, int>;
template <typename T, typename U = foo<T>>
struct bar {};
template <typename T>
using baz = bar<T>;
```
That's the message I get:
```
$ cppcheck --language=c++ --std=c++14 testcase.h
Checking testcase.h ...
[testcase.h:8]: (error) Syntax Error: AST broken, binary operator '>' doesn't have two operands.
```
--
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/834
I am well aware of the Unix Domain socket issue with Geany and `sudo` discussed at length in #1411 and reported by users in #294, #1411, and #1615. However, prior discussion has focused on what Geany's behavior should be when invoked with `sudo` and how users can resolve the issue.
**This situation, where a file in Geany's configuration is invalid for whatever reason, is one that Geany should more facilitate a more graceful recovery from.** Requiring the user to search the internet to discover how to fix the problem, and then having them need to manually delete a configuration file is not a satisfactory user experience.
Specifically, I would suggest that the dialog [found in the code here](https://github.com/geany/geany/blob/935c16ea25374d323ec4212a1a49bdce6… should be modified to include an option for Geany itself to delete the problematic socket (`~/.config/geany/geany_socket_*`), including the potential consequences of this action.
--
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/2102
To edit .md files, l currently use leafpad instead of geany because l don't want to circuitously change the two settings which enable automatic removal of trailing whitespaces just to edit some README.md a bit.
In Markdown, two spaces at the end of the line cause a line break.
l'd like to edit Markdown files with geany without dreading vanished line breaks.
--
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/1464
`\(([^:]+):([0-9]+):([0-9]+))`
--
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/2103
Makers are barely invisible with some themes, or even completely invisible in case of Solarized (light) and Retro. The full list is:
* Bespin
* Dark Colors
* Delt Dark
* GitHub
* Kugel
* Monokai
* Railcasts
* Ralesk's MC
* Retro
* Solarized (light)
* Steampunk
* Tango
* Tinge
--
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-themes/issues/25
){kind=link}