Anybody mind if I add `*.s` and `*.S` to `filetype_extensions.conf` for `ASM`? It's the extension commonly used by/for GCC/GAS.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/904
When I search for some text, I can use the "find" window (`ctrl+f`). In this window I have the "mark" button which can highlight the searched phrase. Sometimes I want to replace some text, and this can be easily done via the "replace" window (`ctrl+h`). In the second case, there's no "mark" button. Often I want to know where exactly the phrase that is going to be replaced appears in the text. In such cases I have to call the "find" window first, mark the text, and then switch to the "replace" window and replace the text. Could you add the "mark" button to the "replace" window?
---
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/972
I believe formerly in 121 or around there, editing of files was allowed Im not sure what happened, but this seems to be the case no longer Pluma, does this operation just fine, as does libre office, and some other file editors When I try to explicitly run geany to open a file across the network, geany will open but the file will not The types of connections
Here it is working in pluma, which is what I would like to see fixed in geany Pluma is a fine text editor, but I like Geany far more
are for me, ssh, and sftp
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/893
With geany 1241 Pretty much any file, even if it has a maximum line length of 80 characters - the horizontal scroll bar is about 300 characters wide, so it's hard to tell if there's a very long line in the file without actually examining each line
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/886
I have selected an executable from a subdir of `E:\Projects` and when pressing the run button it says "The system cannot find the file specified", which is odd since the the "Setup Program" dialog allowed me to select the file using the file dialog, so I know the file exists Perhaps it's just a misleading error message?
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/337
Based on the discussion here https://github.com/geany/geany/issues/921 I tried what is still missing to support opening remote files without gvfs-fuse. As I suspected, there wasn't much missing - mostly some g_file_test() calls which didn't work remotely, file name validation which didn't allow URIs, getting filenames instead of URIs from file dialogs etc.
What works after these patches:
* opening links like https://developer.gnome.org/gio/stable/GFile.html both from command-line and file open dialog
* browsing remote locations in file browser
* opening/saving ftp/ssh/etc. locations when mounted - I guess they need to be mounted to work - even gedit needs them mounted (it would probably be possible to use g_file_mount_enclosing_volume () to pop up dialog to make user mount them, not sure if we want it or not)
* opening/saving remote projects
What doesn't work:
* TM parsing - the only reason here's the g_stat() in tm_source_file_init(), after commenting it out it works but TM at the moment doesn't know about Geany's file operation method used so it's not possible to implement this properly (I plan moving the TM - without ctags - into src making it effectively part of Geany after which it will have access to Geany's definitions)
* File->Properties - I simply have been lazy to implement it
* of course things like find in files, build commands etc. which we cannot run remotely
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/963
-- Commit Summary --
* Add wrappers around g_file_test() and use them everywhere
* Update utils_get_path_from_uri() to return URI when using GIO
* Fix warning in utils_tidy_path()
* Use g_file_new_for_uri() when needed
* Preserve URIs in tm_get_real_path()
* Merge implementations of write_data_to_disk() and utils_write_file()
* Use gtk_file_chooser_get_uris() in file opening/saving dialogs
* Add GIO version of document_rename_file()
* Add GIO implementation to utils_get_file_list_full()
* Add file reading utils function
* Load project config files using the new utility function
* Allow opening projects using URI
-- File Changes --
M plugins/export.c (2)
M plugins/filebrowser.c (6)
M plugins/htmlchars.c (2)
M plugins/saveactions.c (6)
M src/build.c (4)
M src/callbacks.c (8)
M src/dialogs.c (8)
M src/document.c (131)
M src/editor.c (2)
M src/highlighting.c (6)
M src/keybindings.c (4)
M src/keyfile.c (4)
M src/libmain.c (24)
M src/msgwindow.c (6)
M src/plugins.c (2)
M src/project.c (57)
M src/symbols.c (2)
M src/templates.c (2)
M src/ui_utils.c (6)
M src/utils.c (322)
M src/utils.h (16)
M src/vte.c (2)
M src/win32.c (4)
M tagmanager/src/tm_source_file.c (16)
-- Patch Links --
https://github.com/geany/geany/pull/963.patchhttps://github.com/geany/geany/pull/963.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/963
The plugin seems to not collapse the directory containing the active document, but it collapses others in the tree view when reloading. It would be cool if it kept all directories that are expanded before the reload, expanded after, provided they still exist.
---
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/415
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