> ... IIRC @avafinger applied changes manually, it would be nice for someone to
> test the PR explicitly.
Sure. However, as you probably could see, the changes are very much limited, so
applying manually should be just as effective. Of course, I did the testing of
the issue, as I described
@nomadbyte pushed 1 commit.
aa40d7cc1d6b415a7fd4bde4593193beb31f3e79 Debugger: Fix debugging of
multi-threaded programs
--
View it on GitHub:
https://github.com/geany/geany-plugins/pull/1170/files/0abd437f60141bd63a1b5dc1aab9b042e5ae3f3e..aa40d7cc1d6b415a7fd4bde4593193beb31f3e79
You
Updated Ukrainian translations of several messages; also updated the source
file references.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1208
-- Commit Summary --
* po: Update Ukrainian translation
-- File Changes --
M
For some reason this fix did not make it into the 1.38. Is there any more
details needed for this?
--
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/pull/1028#issuecomment-940405095
Adding to what @elextr mentioned, the default encoding (for new files) is
actually set in Preferences > Files.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
It's quite trivial to change GeniusPaste to call
`soup_session_new_with_options()` instead of the current
`soup_session_async_new_with_options()`, the resulting object is still the
`SoupSession`, and it seems that the plugin is in fact doing a **synchronous**
send. We can implement the
Apparently, using tilde-delimited code blocks within a list seems to work ok:
Just for the reference, the Scintilla's Markdown lexer:
Is Common Mark what Scintilla uses for Markdown spec in their implementation?
--
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/1070#issuecomment-822884346
The common syntax for the Markdown image is `` (see
[md-images]).
Not sure if the alt-text should be considered optional by the markdown parser
(in HTML it is optional) . Alt-text is useful for textual labeling of the image
and used by screen readers too. IIRC, specifying
LaTeX v0.7, Geany 1.36 (Ubuntu)
- menu:`Preferences > Keybindings > LaTeX > Insert Itemize List => Ctrl+Alt+M`
- menu:`File > New`
- menu:`Document > Set Filetype > Markup Languages > LaTeX source file`
- in the new document: `Ctrl+Alt+M`
Result:
```
\begin{itemize}
\item
\end{itemize}
Looking closer, it's clearly a problem with the way Debugger processes the
thread's call-stack. Somehow it removes the current function frame from the
stack on stepping (`doSomeThing < start_thread < clone`). This triggers the UI
to process the next item in the stack (`start_thread`), so it
> ...so things like "wants to debug thread_start" are actually referring to GDB
Well, Scope does not seem to have this issue (i.e. trying to break in
`pthread_create` and `clone`). They are properly reported on the Stack. This
must be an issue, which is specific to thread-handling code in
Not a solution, but you may try to use
[Scope](https://plugins.geany.org/scope.html) -- that's another DBG plugin for
Geany. It also supports threads and seems to cope somewhat better with
following the thread context. In your example, Scope will even show two
execution-line pointers for each
@nomadbyte commented on this pull request.
> @@ -87,7 +87,7 @@ static const gchar *translators[][2] = {
{ "sv", "Tony Mattsson superx...@gmail.com" },
{ "sr", "Nikola Radovanovic cobis...@gmail.com"},
{ "tr", "Gü
@nomadbyte pushed 1 commit.
7b7f0def021715a44ac1e8c3938becb28270b71f PO:(uk) Update translation
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://github.com/geany/geany/pull/2724/files/fba639faf61170b17ca20314b8be662e4eacf97b
```
...
23:05:00: SpellCheck DEBUG : Initializing Enchant library version 2.2.5
23:05:00: (NULL) WARNING : Error loading plugin: 'C:\Program Files
(x86)\Geany/lib/enchant-2\enchant_aspell.dll': The specified module could not
be found.
...
```
This appears as some odd path issue:
Which Geany version are you using? How did you install it?
GeanyVC plugin is dependent on `libgtkspell`, which in its turn depends on
`libenchant`. The spellcheck is used for the commit message/comment (when
language is configured in the plugin's Preferences).
--
You are receiving this
@nomadbyte pushed 1 commit.
fba639faf61170b17ca20314b8be662e4eacf97b PO:(uk) Update translation
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://github.com/geany/geany/pull/2724/files/8676879cf7f8d5b757ed08b3e94ea3d35c0f0c89
Fixes #2723 . More like an overhaul; covers UI messages for the main core and
the integrated plugins; reviewed and cross-checked.
Hopefully, with better localization Geany may integrate more seamlessly into
the Ukrainian localized usage, at least in the case of Linux-based workflow.
You can
Not sure how much use Geany has seen in Ukrainian, but the current
uk-translation appears very much incomplete (~48%).
--
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/2723
> Do you get a message when you do `Menu->Document->Line Wrapping which calls
> editor_set_line_wrapping()`?
Same Gtk-Warning only when **unsetting** the "Line Wrapping". That is the
wrapping activation works Ok and shows no warning, clearing the active wrapping
produces the warning.
In general, this issue results in incorrect intialisation of the editor's
horizontal scrollbar (at least on my platform, see the Geany-INFO in OP)
Further debugging yields more pointers at the cause of this issue.
The warning seems to result from `Scintilla::ScintillaGTK::Resize()` call
Below is a test file (test-long-line.txt) that produces the warning.
The steps to trigger the warning:
1. Start from a clean configuration, disable plugins
```
G_MESSAGES_DEBUG=all geany -v -p -c test-config
```
2. Open the test-long-line.txt
3. Turn *Preferences>Editor[Features]:Line wrapping:
Geany 1.38 shows a Gtk-Warning at startup
```
(geany:29297): Gtk-WARNING **: 00:58:33.911: Negative content height -6
(allocation 1, extents 7x0) while allocating gadget (node scrollbar, owner
GtkScrollbar)
```
This seems to be triggered when:
1. the file being opened at startup contains a long
I was trying to make sense of the Geany's Auto-indent modes {Basic, Current
chars, Match braces}, as listed in Preferences>Indentation:Auto-indent mode.
It's absolutely not clear [to me] from the names what these modes do and how
they differ. Trying them out in practice still shows little
Fixes #1045 . Covers UI messages for all 45 of the current plugins, reviewed
and cross-checked.
By the way, this turned out to be a curious way to catch some existing
issues/quirks with current plugins. Likely most of these issues have been
logged by users already.
You can view, comment on, or
I guess, it's demand-and-supply kind of issue... Still, the Ukrainian
localization for Geany plugins is missing altogether.
--
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/1045
Without getting into semantics of "vanilla", exuberant-ctags is listed as a
dependency for [geany-plugin-ctags
package](https://packages.ubuntu.com/focal/geany-plugin-ctags) on Ubuntu.
So it will be fetched automatically for anyone getting Geanyctags plugin . This
is how exuberant-ctags found
Thanks for suggesting the alternative.
Perhaps, we should consider fixing Geanyctags to work with "vanilla" `ctags`,
as this one is likely more commonly installed by default.
I don't mind submitting the patch to restrict the `find` to `-type f`. This
should not cause any issues, so far as I
Digging more into this... Obviously, this appears to be a known issue in
[geanyctags.c](../blob/bc4dc07e4deb694b647977791a23af6776db4644/geanyctags/src/geanyctags.c#L234-L250)
(albeit conditionally handled for Windows only).
Looks like the issue is tied to the output from the `find` command
Using Geanyctags 1.38 on Ubuntu 20.04.
On first use the 'Project > Generate tags' menu command completes correctly and
generates a new .tags file for the project. After that, trying to re-generate
the tags (repeat 'Generate tags') fails with the following error in the
Messages pane:
```
find
Here's a little test setup to formalize the use-case:
```
mkdir r1
cd r1
git init
echo "f1" >> f1
git add f1
git commit -a -m "added f1"
git config user.name testuser
git config user.email testuser@
git commit -a -m "added f1"
git worktree add ../w1 -b work1
echo "f1:r1" >> f1
git status
cd
Geany has a handy action in its editor context menu 'Open Selected File' which
will parse text under cursor to get a file-path and then open the file in a new
tab. This is very useful when opening some file references like those in
include directives etc.
It'd be nice if this action were also
Fixes #1032.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1033
-- Commit Summary --
* GeanyVC: Correct the displaying of tooltip for the attach to menubar action
-- File Changes --
M geanyvc/src/geanyvc.c (2)
-- Patch
In the GeanyVC Plugin Preferences the **"Show VC entries at editor menu"**
setting is showing incorrect tooltip. It's somewhat confusingly explains this
as:
> "Whether menu for this plugin are getting placed either inside tools menu or
> directly inside Geany's menubar."
This tooltip seems
Update po-files related to #1029, part of fix for #251 .
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1030
-- Commit Summary --
* GeanyVC: Show ellipsis in menu items requiring further user input (po
update)
-- File Changes --
GeanyVC is just as lightweight as the Geany itself :)
So in editor context GeanyVC rather assumes that the underlying repositories
have been properly set up, which includes logins credentials needed for clone,
pull (if any). This way GeanyVC does not need to deal with managing the logins
for
> This seriously reduces the usefulness of the otherwise great feature of being
> able to use an external diff viewer.
Not sure what your workflow is. Geany does block, but the external diff tool is
not getting blocked. Moreover, you may as well make edits to the current
version of the file
Cannot reproduce since [v1.36](../releases/tag/1.36.0).
Likely related to #741 and #970. Fixed in #967 .
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Fixes #251.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1029
-- Commit Summary --
* GeanyVC: Show ellipsis in menu items requiring further user input
-- File Changes --
M geanyvc/src/geanyvc.c (4)
-- Patch Links --
Fixes #285.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1028
-- Commit Summary --
* GeanyVC:(Git) Fallback to `git rev-parse` for getting the
repo/worktrees top directory
-- File Changes --
M geanyvc/src/vc_git.c (44)
Fixes #837.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1026
-- Commit Summary --
* GeanyVC: Report a completion status of the commit command
-- File Changes --
M geanyvc/src/geanyvc.c (28)
M geanyvc/src/vc_git.c (2)
Fixes #573.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1025
-- Commit Summary --
* GeanyVC: Support the use of external diff-tool in directory context
-- File Changes --
M geanyvc/src/geanyvc.c (149)
M
Could the version-sort be done with `strverscmp()` instead of `filevercmp()`
from coreutils?
There're some differences, but for the general use like "file-1.9" vs.
"file-1.10" the `strverscmp()` should do just fine. And it's part of `glibc`
(well, `#define _GNU_SOURCE 1`), so no need to copy
Same symptoms as issue #970; fixed in #971.
--
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/741#issuecomment-725114422
We can consider using GitHub workflow actions for this. For example,
[actions/issue-label-notifier](https://github.com/marketplace/actions/issue-label-notifier)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Accepting maintainership of the GeanyVC plugin per @frlan invitation.
It would be nice to have GitHub notify @nomadbyte anytime an issue/PR is
labeled with [plugin/geanyvc](../../labels/plugin/geanyvc) tag.
You can view, comment on, or merge this pull request online at:
https://github.com
Fixes #1003
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1004
-- Commit Summary --
* GeanyVC:(Fossil) Limit the width of the history log/timeline output
-- File Changes --
M geanyvc/src/vc_fossil.c (2)
-- Patch Links --
The Fossil history log/timeline entries are printed in single lines in VC-LOG
editor tab.
When a log's commit message is very long, it requires a lot of horizontal
scrolling. This may be tedious and inconvenient.
It should be possible to limit the width of the Fossil log to some reasonable
Superseded with #1001 (changed the PR's branch name)
--
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/pull/1000#issuecomment-678538435
Fixes #999
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1001
-- Commit Summary --
* GeanyVC:(Fossil) When edited file is not in the repo, simply return; no
assert needed
-- File Changes --
M geanyvc/src/vc_fossil.c (1)
Closed #1000.
--
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/pull/1000#event-3681290099
I added a separate issue and a PR with the fix [#1000]
--
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/pull/971#issuecomment-678506536
Fixes #999
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1000
-- Commit Summary --
* GeanyVC:(Fossil) When edited file is not in the repo, simply return; no
assert needed
-- File Changes --
M geanyvc/src/vc_fossil.c (1)
Looking closer, this happens when requesting (opening) 'Version Control' menu
on any current file that is not under any supported VCS, that is being
"untracked".
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@frlan reported:
Seeing
```
(geany:38): GeanyVC-CRITICAL **: 20:47:43.400: parse_fossil_info: assertion
'start' failed
(geany:38): GeanyVC-CRITICAL **: 20:47:43.725: parse_fossil_info: assertion
'start' failed
```
while using the code.
--
You are receiving this because you are
Which version of the Fossil client are you using?
If it's the recently released 2.12, then there was an update to 'fossil info'
command. I have a fix for this, but was delaying it until the 2.12 version is
released.
--
You are receiving this because you are subscribed to this thread.
Reply to
> And to add to that, local administrators will distribute the software with
> the default option, that most certainly picks a translation locale, an
> unwanted effect when the option of language is unclear overal and the
> software is suited to programming (a task mainly done in English).
At
Could I do anything else to have this PR/issue resolved? I'd readily answer any
questions, in case you guys (? @frlan ) have any about this.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@eht16 , @elextr Do you guys need any more input from me on this to get the PR
going?
--
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/www.geany.org/pull/22#issuecomment-631588100
Fixes #976
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/977
-- Commit Summary --
* GeanyVC: Use geanyvc_la_LIBADD to add libs needed for unittests
-- File Changes --
M geanyvc/src/Makefile.am (2)
-- Patch Links --
Looks like the recent build of [90974ab] is failing at linking geanyvc
unittests due to missing gtkspell lib:
[jobs/685847261](https://travis-ci.org/github/geany/geany-plugins/jobs/685847261#L7195)
```
...
CCLD unittests
unittests-geanyvc.o: In function `vccommit_activated':
> I don't think its as simple as first thoughts indicate, project files don't
> get stored in the tree by default..
What is the purpose of `base_path` project setting? It's logical to use it in
conjunction with project's source tree. Such that any relative paths referenced
in `[files]` would
Thanks for your comments, I addressed them in two batches. The updated version
is in commit [fa8f646]
--
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/www.geany.org/pull/22#issuecomment-623129574
@nomadbyte commented on this pull request.
> @@ -86,21 +86,49 @@ for remote files, so there is no need to disable this
> setting with Geany 0.16.
## How can I change the language of the user interface?
-On Windows: Download https://download.geany.org/contrib/geany_english.bat
-a
@nomadbyte pushed 1 commit.
fa8f64667578d39ad569da4f344a0cc8b8b1ce45 Clarify the use of English as an
example of target UI language.
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://github.com/geany/www.geany.org/pull/22/files
@nomadbyte commented on this pull request.
> @@ -86,21 +86,49 @@ for remote files, so there is no need to disable this
> setting with Geany 0.16.
## How can I change the language of the user interface?
-On Windows: Download https://download.geany.org/contrib/geany_english.bat
-a
@nomadbyte pushed 1 commit.
3b9426a30e51d9ba29afcf149d3b73aed520a446 Edit wording in How to change UI
language section.
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://github.com/geany/www.geany.org/pull/22/files
@nomadbyte commented on this pull request.
> @@ -86,21 +86,49 @@ for remote files, so there is no need to disable this
> setting with Geany 0.16.
## How can I change the language of the user interface?
-On Windows: Download https://download.geany.org/contrib/geany_english.bat
-a
> Doesn't here (nor does chrome), maybe an option somewhere (like Geany :)
I'm running a vanilla Ubuntu 18.04 on this box, Firefox 75, here from this
window I click on + to add a new tab, it opens up at the very end of my
"millions" of opened tabs; I click on whatever bookmark to browse in the
It's certainly good that it's configurable, at least that the history behavior
could be enabled.
However, it would make sense to reverse the default, based on the "least
surprise" UI rule. This is especially apparent while using Version Control (or
any other plugin that opens some transient
Thanks. Any reason for this not to be a default behavior?
--
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/2488#issuecomment-620956244
`geany 1.36 (git >= 825acb21) (built on 2020-04-28 with GTK 3.22.30, GLib
2.56.4)`
When Editor has multiple tabs, closing a given tab does not open the previous
(in viewing/location history). Instead it opens a next (to the right) tab, or a
previous (to the left) if there's no next.
This is
Addresses #1757, describes the workarounds mentioned in the issues
discussion.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/www.geany.org/pull/22
-- Commit Summary --
* Describe how to change UI language by editing Geany shortcut
-- File Changes
Confirmed. Swapping Scintilla version used in Geany version 1.32 with one from
1.34 resolved this issue. There was some rework in Scintilla editor classes
around selection and scroll handling.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or
This is not about the theme, unfortunately. It seems to me that it was likely a
bug in Scintilla. I can't zero in on exactly what their fix was. But this all
seemed to be be related to transition to GTK3. BTW, the nightlies look like
built to GTK2, otherwise they'd comply with my current GTK3
@nomadbyte commented on this pull request.
> +
+ if (std_out)
+ {
+ std_out1 = *std_out;
+ *std_out = NULL;
+ }
+ if (std_err)
+ {
+ std_err1 = *std_
D you know if this this issue has been specifically fixed since 1.32, or "It
just works"?
Btw, 1.37 is not released (even 1.36 is not pullable from Ubuntu repos yet). I
tried a nightly, and Geany seems to use a different theme internally, unlike
the rest of the installed apps (Firefox,
I'm experiencing the same issue on Ubuntu 18.04. Though the appearance is
different. The scroll marker (in my vanilla Ubuntu install it's orange colored)
is not properly cleared on movement and eventually the whole vertical scroll
bar turns orange.
I'm not uploading a screenshot, but here's
Fixes #970.
Enabling Editor context menu in config options creates a new instance of File
menu in addition to the one under Tools Version Control. Its properly
attached to its parent. However, updates are done only to a single instance
(basically the last one to initialize), which in this case
Using GeanyVC with Geany 1.36 on Ubuntu 18.04.
When I enabled plugin configuration options: "Show VC entries at editor menu".
The menu was added to Editor context menu (right-click menu), this is in
addition to the menu under Tools in main menu.
For a given managed file (already in repo), the
Here's a test repo to try out the PR #969 :
```
mkdir newrepo && cd newrepo
fossil init ../newrepo.fossil
fossil open ../newrepo.fossil
echo "Test file" >> testfile.txt
fossil add testfile.txt
fossil status
fossil commit -m "Added testfile"
```
Now in Geany, open the `newrepo/testfile.txt` and
@zaher : This workaround is probably the easiest to do (as described above).
Especially so to students who want to learn some coding. This could be an
"extra credit" kind too, but too easy really :)
--
You are receiving this because you are subscribed to this thread.
Reply to this email
Yep, this could be an entry in FAQ or Manual.
Something like "How to change Geany's UI language from OS default?". This would
cover both Windows and Linux/Unix-like systems. BTW, in case of Linux the
approach is similar: Set the language env variable prior to launching Geany
(could be LANG,
Well, I might be late to the party... Well, I just faced the very same
question. Now with Geany at 1.36 release on Windows.
Here's a minimally invasive solution:
Change the installed **Geany Shortcut** to set the `LANG` variable to the
desired AND __supported__ by your system's C API language.
This is the follow up to #968
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/969
-- Commit Summary --
* GeanyVC: Add support for Fossil SCM (fossil-scm.org)
-- File Changes --
M geanyvc/README (8)
M
I'm using [Fossil SCM](https://fossil-scm.org) with most of my projects, as
it's free, quite lightweight yet mighty just like Geany :). Apart from
distributed Version Control, Fossil also packs Issue tracker, Wiki, Forum, and
Server all in single binary executable. So pretty much all I need for
87 matches
Mail list logo
