Hi. I am working on Ubuntu 18.04. Geany and geany-plugins 1.38 compiled from sources.
I experienced that, if in the file:
- ~/.local/lib/python3.6/site-packages/altre-cartelle.pth
there is any non strictly ASCII byte, the debugger will not start when the Run button is clicked. Executing geany from the console, I can read the output:
Failed to import the site module
Traceback (most recent call last):
File "/usr/lib/python3.6/site.py", line 570, in <module>
main()
File "/usr/lib/python3.6/site.py", line 556, in main
known_paths = addusersitepackages(known_paths)
File "/usr/lib/python3.6/site.py", line 291, in addusersitepackages
addsitedir(user_site, known_paths)
File "/usr/lib/python3.6/site.py", line 213, in addsitedir
addpackage(sitedir, name, known_paths)
File "/usr/lib/python3.6/site.py", line 169, in addpackage
for n, line in enumerate(f):
File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 66: ordinal not in range(128)
Removing the non ASCII bytes, the debugger runs without problems.
Ciao.
Massimo
My native language is not English, please excuse me any incorrectness, I apologize for any inconvenience caused, thank you
--
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/1143
I use `cargo check` frequently.
https://doc.rust-lang.org/cargo/commands/cargo-check.html
```Check a local package and all of its dependencies for errors. This will essentially compile the packages without performing the final step of code generation, which is faster than running cargo build. The compiler will save metadata files to disk so that future runs will reuse them if the source has not been modified.```
One problem with this patch though. As I moved the 3 items down, putting `Cargo Check` at the top. When I test my patch, I get the dialog to enter custom text when selecting `cargo build`, but before it was when selecting `cargo test`. I couldn't figure out where geany was getting the instruction to pop up a dialog, as all those fields are the same, both in the filetypes.rs file, and when looking at them from the Geany build menu.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2573
-- Commit Summary --
* Add "cargo check" to build commands
-- File Changes --
M data/filedefs/filetypes.rust (15)
-- Patch Links --
https://github.com/geany/geany/pull/2573.patchhttps://github.com/geany/geany/pull/2573.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/2573
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2149
-- Commit Summary --
* .travis.yml:add tests for gcc 7 and 8
* use build matrix #2139
* for gcc 8, specify xenial and the correct version
* try globalizing the GTK3 env directives
* try indenting the matrix to get global to work
* revert a little
* fix indentation
* add clang 5 test (closes #2139)
* only run `make distcheck` for a single job
* specify dist and compiler explicity
* remove unneeded hyphenated lines
* add DISTCHECK_ONLY, don't hide it under gcc-5
* use xenial instead of trusty
* reduce clang to 3.5
* try default clang on xenial
* try default clang on trusty
* clang:revert to using 5.0 on trusty
* allow clang to fail
* remove cache directive, try clang 3.5 again; also...
* specifying 3.5 on trusty
* install libc++
* clang:explicity enable C++11 support
* make:temporarily add -n and VERBOSE=1
* use clang 3.8
-- File Changes --
M .travis.yml (77)
-- Patch Links --
https://github.com/geany/geany/pull/2149.patchhttps://github.com/geany/geany/pull/2149.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/2149
This includes patches by @b4n in #2149
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2574
-- Commit Summary --
* .travis.yml:add tests for gcc 7 and 8
* use build matrix #2139
* for gcc 8, specify xenial and the correct version
* try globalizing the GTK3 env directives
* try indenting the matrix to get global to work
* revert a little
* fix indentation
* add clang 5 test (closes #2139)
* only run `make distcheck` for a single job
* specify dist and compiler explicity
* remove unneeded hyphenated lines
* add DISTCHECK_ONLY, don't hide it under gcc-5
* use xenial instead of trusty
* reduce clang to 3.5
* try default clang on xenial
* try default clang on trusty
* clang:revert to using 5.0 on trusty
* allow clang to fail
* remove cache directive, try clang 3.5 again; also...
* specifying 3.5 on trusty
* install libc++
* clang:explicity enable C++11 support
* make:temporarily add -n and VERBOSE=1
* use clang 3.8
* use clang 3.5, add missing "compiler" line
* Major Travis update
-- File Changes --
M .travis.yml (105)
-- Patch Links --
https://github.com/geany/geany/pull/2574.patchhttps://github.com/geany/geany/pull/2574.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/2574
At the moment, when creating a project, the user is greeted with the
dialog containing:
1. Name
2. Filename
3. Base path
The user is expected to type the name of the project into (1), and then,
Geany tries to guess the base path and file name. The guess simply takes
the project directory specified in settings and appends the name. When the
project is located anywhere else than in the projects directory,
the guessed values are wrong and have to be entered manually which is
quite annoying. In addition, the dialog doesn't make it clear that the
user should start with (1), when he starts with (2) or (3), he has to
fill in all 3 values manually.
I think we can do better - instead of entering the project name and
guessing base path based on that, we can go the other way round; first,
get the base path and then, from the base path provided by the user,
set the project name and project file.
With this approach, Project->New:
a. First pops up a open directory dialog to specify base path
b. After that, opens the (currently used) New Project dialog which
is pre-filled in the following way:
1. Name: The last directory in base_path
2. Filename: depending on "store project file inside the project base
directory" settings either in base_path/(1).geany or projects_dir/(1).geany
3. Base path: path specified in (a)
This way, in most cases, the user will only have to select the base
directory in the first step and use the pre-filled values without
any modification no matter whether the project is stored in the projects
directory or not.
The other 2 patches:
1. Simplify configuration of the project by automatically opening the project properties dialog upon project creation.
2. Use "Store project file inside the project base directory" by default
For more description of these 2 patches, see the commit messages.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3018
-- Commit Summary --
* Improve user experience when creating new projects
* Automatically open Project Properties dialog upon project creation
* Store project files in base directory by default
-- File Changes --
M src/keyfile.c (2)
M src/project.c (67)
M src/ui_utils.c (15)
M src/ui_utils.h (2)
-- Patch Links --
https://github.com/geany/geany/pull/3018.patchhttps://github.com/geany/geany/pull/3018.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/3018
Geany version: 1.33
If the compilation of file A modifies file B, the scrollbar in file B doesn't move after the compilation.
How to reproduce:
1. Start compilation of some file. It has to modify another opened file.
2. Switch to the other file that has been modified by the compilation.
3. In appearing message window, "The file _\<filename\>_ on the disk is more recent than the current buffer.", reload the file.
4. Finished. Now the scrollbar of the modified file won't move
[Here is a video of the bug reproduction (zipped)](https://github.com/geany/geany/files/2169464/geany-bug-demonstrati…).
--
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/1893
@thwaller Geany print to PDF will print the markdown source, it will not convert the markup to PDF (which it sounds like you expect). You can define a build command to convert to run your markdown converter to pdf and print.
Colour printing of the source is intended to replicate the way the source is styled in the editor pane, but it was not designed to handle the current prevalence of dark themes.
--
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/617#issuecomment-985118195
Are there any updates on this? I have never needed or used the printing functionality before. I started trying it now as Typora, the markdown software I was using, changed to paid software. So I thought to give Geany a shot as being the new editor. For me, I do a lot of export to pdf, which Geany does not provide as an option, even in extensions from what I can see. I can however print to file -> PDF. I am using `Kugel` appearance and my print output is as described here... a white page with text I cannot read, it is almost white.
Just sharing my opinion, I see little need for color printing in Geany. Maybe I am wrong and others do. That said, I concur with the idea of making the default print output as monochrome, maybe even with the ability to change the opacity of the printing, like 50% to 100% or something.
I wanted to add my scenario so current circumstance that this is needed, is an issue, can be seen. While Geany is not really a "markdown editor", I think it now has more use to me. Any time I can reuse existing software, that is a good thing :)
--
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/617#issuecomment-985111171