I find this helpful when replicating documents since you wouldn't have to browse through the original directory when renaming the document when it's untitled. You also get to have a pattern from the original filename. It becomes very convenient along with in-place renaming.
I'm happy with how it is but perhaps people would want it to be configurable so that it can be disabled, or given with a different naming format. The latter wouldn't sound easy though.
Reasons for choosing `.copy-xx:`
- Lowercase because it's less noisy.
- A dash to make it more distinguishable with the numbers.
- 2 digits because it's good enough. 1-digit is a little conservative. 3-digits is overkill.
- Prefixed with '.copy' because `.xx` files could exist and could confuse the user; and '.copy' over '.clone' because it's shorter, and it's also common among some file managers, I think.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1191
-- Commit Summary --
* Give '.copy-xx' filenames to cloned documents
* Do not set cloned documents as readonly
-- File Changes --
M src/document.c (36)
-- Patch Links --
https://github.com/geany/geany/pull/1191.patchhttps://github.com/geany/geany/pull/1191.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/1191
I use Geany as the external editor for my file managers (Krusader, Double Commander etc.). One very common operation is to open a file in the edit, inspect it for a few seconds (scrolling around), then exit, ideally without keeping the file as an open tab, since it wasn't opened from Geany itself, but rather from the file manager, typically while checking out a large number of files (e.g. the source files of a project).
To do this, I currently have to press Ctrl+W, then Alt+F4 (or <Primary>+Q). It would be really nice if I could define Esc as a key binding for exiting Geany, if it's pressed in the main window. Is there a way to do that? (I tried Keybindings, but pressing Esc closes the dialog that records the shortcut).
---
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/1124
Confirmed with 1.29 Git.
@techee the fix is probably in the Python parser not to generate null symbols, tried Pascal and Rust with null function names (both languages that have a syntactic indication of function declaration) and no error. I guess fixing the parser means upstream. But possibly tagmanager should ignore not complain either.
--
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/357#issuecomment-243302003
I am using Geany-1.27 and I started noticing the same issue when editing a python file. I could replicate the issue when editing a python class with a function definition inside. If you define a function but do not name it like this
```python
def (self, args)
```
anytime you type anything else in the file, I get the warning in the terminal window. As soon as you complete the function name,
```python
def function(self, args):
```
the warning stops printing to screen. The function does not have to be in a class. Hope this helps!
--
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/357#issuecomment-243199923
Sorry for the late answer. Yes, I can confirm it is, indeed, a GTK problem.
--
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/511#issuecomment-243171931
The "Start in:" field in the Geanly.lnk should be empty, it's currently set to the install dir and this prevents command-line invocations from opening relative-pathed file arguments correctly.
Also it would be useful for scripting/debug to have a mode where geany stays attached to the launch cmd console (`start "" /B /WAIT "C:\Program Files (x86)\Geany\bin\Geany.exe"` is a possible work-around)
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/786
Invoking `C:\Program Files (x86)\Geany\Geany foo.txt` for some existing file `foo.txt` in your current dir (or at any relative path) fails because the link has a "Start in:" value set; leaving this empty makes it work as expected.
--
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/1183
Patch from https://github.com/geany/geany/pull/1177#issuecomment-241438625, plus an attempt at considering the current scope (which is likely riddled with bad stuff, but still a POC).
I can drop the second (toy) patch if the first is interesting enough, and possibly make a separate PR afterward if it's somehow interesting still. In any case, reviewing each commit separately is likely a better approach.
@techee @krogank9
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1188
-- Commit Summary --
* Add support for scoped calltips
* FXIME: Attempt at using the current (implicit) scope for symbol scope search
-- File Changes --
M src/editor.c (155)
-- Patch Links --
https://github.com/geany/geany/pull/1188.patchhttps://github.com/geany/geany/pull/1188.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/1188