I have configured some build commands for my project:
In Commander, I can invoke independent commands (such as “Run tests”) and execute commands (such as “Run on test input”), but not filetype-specific commands (such as “Pylint”). It seems like Commander just doesn’t see their labels:
---
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/462
As far as I can find, Geany will only use the line endings specified in "Preferences / Files / Default end of line characters" when it creates new files. Existing files will keep their line endings, unless you check the "Ensure consistent line endings" box, in which case I suppose Geany will find out what type of line ending is in the majority, and use that throughout the file.
What I would like is an option to always, unconditionally, force the default line ending to be applied when saving any file, whether newly created or previously existing.
---
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/984
Here are some changes to lineoperations; adding selection support.
If a selection is made in the file, the line operation will be applied to the lines within the selection, rather than the whole file.
Like usual, I'm open to hear any suggestions/improvements.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/378
-- Commit Summary --
* lineoperations: combined similar code
* lineoperations: added selection support
* lineoperations: removed unnecessary parameters
* lineoperations: added selection to documentation
* lineoperations: added some ui changes
* lineoperations: minor formatting
-- File Changes --
M lineoperations/ChangeLog (6)
M lineoperations/README (14)
M lineoperations/src/linefunctions.c (340)
M lineoperations/src/linefunctions.h (28)
M lineoperations/src/lineoperations.c (237)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/378.patchhttps://github.com/geany/geany-plugins/pull/378.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/378
No matter what I do, Geany won't highlight any .INO syntax! I tried copying (geany root)/data/filetypes.cpp to filetypes.ino (.INO syntax is about the same as .CPP syntax). No luck. I need .INO syntax highlighting! Can someone help me?
FILETYPES.INO listing:
```cfg
# For complete documentation of this file, please see Geany's main documentation
[styling=C]
[keywords]
# all items must be in one line
primary=alignas alignof and and_eq asm auto bitand bitor bool break case catch char char16_t char32_t class compl const const_cast constexpr continue decltype default delete do double dynamic_cast else enum explicit export extern false final float for friend goto if inline int long mutable namespace new noexcept not not_eq nullptr operator or or_eq override private protected public register reinterpret_cast return short signed sizeof static static_assert static_cast struct switch template this thread_local throw true try typedef typeid typename union unsigned using virtual void volatile wchar_t while xor xor_eq
secondary=
# these are the Doxygen keywords
docComment=a addindex addtogroup anchor arg attention author authors b brief bug c callergraph callgraph category cite class code cond copybrief copydetails copydoc copyright date def defgroup deprecated details dir dontinclude dot dotfile e else elseif em endcode endcond enddot endhtmlonly endif endinternal endlatexonly endlink endmanonly endmsc endrtfonly endverbatim endxmlonly enum example exception extends file fn headerfile hideinitializer htmlinclude htmlonly if ifnot image implements include includelineno ingroup interface internal invariant latexonly li line link mainpage manonly memberof msc mscfile n name namespace nosubgrouping note overload p package page par paragraph param post pre private privatesection property protected protectedsection protocol public publicsection ref related relatedalso relates relatesalso remark remarks result return returns retval rtfonly sa section see short showinitializer since skip skipline snippet struct subpage subsection subsubsection tab
leofcontents test throw throws todo tparam typedef union until var verbatim verbinclude version warning weakgroup xmlonly xrefitem
[lexer_properties]
styling.within.preprocessor=1
lexer.cpp.track.preprocessor=0
preprocessor.symbol.$(file.patterns.cpp)=#
preprocessor.start.$(file.patterns.cpp)=if ifdef ifndef
preprocessor.middle.$(file.patterns.cpp)=else elif
preprocessor.end.$(file.patterns.cpp)=endif
[settings]
lexer_filetype=C
# default extension used when saving files
extension=cpp
# MIME type
mime_type=text/x-c++src
# the following characters are these which a "word" can contains, see documentation
#wordchars=_abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789
# single comments, like # in this file
comment_single=//
# multiline comments
comment_open=/*
comment_close=*/
# set to false if a comment character/string should start at column 0 of a line, true uses any
# indentation of the line, e.g. setting to true causes the following on pressing CTRL+d
#command_example();
# setting to false would generate this
# command_example();
# This setting works only for single line comments
comment_use_indent=true
# context action command (please see Geany's main documentation for details)
context_action_cmd=
[indentation]
#width=4
# 0 is spaces, 1 is tabs, 2 is tab & spaces
#type=1
[build-menu]
# %f will be replaced by the complete filename
# %e will be replaced by the filename without extension
# (use only one of it at one time)
FT_00_LB=_Compile
FT_00_CM=g++ -Wall -c "%f"
FT_00_WD=
FT_01_LB=_Build
FT_01_CM=g++ -Wall -o "%e" "%f"
FT_01_WD=
FT_02_LB=_Lint
FT_02_CM=cppcheck --language=c++ --enable=warning,style --template=gcc "%f"
FT_02_WD=
EX_00_LB=_Execute
EX_00_CM="./%e"
EX_00_WD=
```
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/715
Now the GIO path fully uses GIO both for loading and saving documents, it could be useful to fully support GVFS path-less URIs, i.e. without gvfs-fuse.
Apparently it would help some people on weird systems like OpenBSD which just removed it or something.
It's however tricky as we currently assume we have a local path. Some things that need to be done:
- [ ] allow for not having a local path (likely breaks plugin API)
- [ ] make TM work without a local path
- …
---
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/1145