As the conflict was between my normal user and root (which **all linux users
will have**) I decided to take action:
1) Wrote a Perl script that finds the owner of the file passed in the argument
If is root, appends a **sudo** in front of the command
2) Replaced "geany %F" in
Not shouting, emphasis
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3871#issuecomment-2120093612
You are receiving this because you are subscribed to this thread.
Message ID:
Instead of an alert and impeding the user to open, a more **elegant** approach
would be a colored bar on the top as it shows when it's going to be
overwritten saying that ** the file is in read-only mode**!
--
Reply to this email directly or view it on GitHub:
Other mature editors let you open the file without this disgusting and policial
alert. They only do not allow to save, but OPENING TO VIEW the content, mature
editors like Vim, Gediit and all others is OK. Only Geany Iimpedes you to EVEN
open the file!!
--
Reply to this email directly or
I had a script with n variable, wanted to switch to TOTAL
Open replace window
type n
choose Whole word only
It will get '\n' too and IMHO I think it should SKIP new lines, because if
Geany replace them, the text would be destroyed.
--
Reply to this email directly or view it on GitHub:
Python has different extension files. Apart from .py it has one with an "i" at
the end: ".pyi" files.
How to configure Geany to allow Format > Comment in types Geany do not
recognize? How would I configure for a new filetype wheter to use // or # or "
in comments ?
--
Reply to this email
It is very borring to click on a textfile and Geany gives an Erro Window: You
accessed with the socket of other user.
Avoid this JUST ADDING A "-i" in the geany.desktop (/usr/share/applications)
in linux at the "Exec line"
Now on Line 142: Exec geany %F
Better usability
if the software prints the **string colors** AFTER **scalar and identifier_1**
color, these colors are ovewritten by string color, and that seems to be the
deep problem.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3860#issuecomment-2081494130
Have done that, opened via Tools, replaced all the file content with the
configs you suggested and still not working.
I closed geany, reopened, and even think that **bash** is taken by geany as
**sh** too ?
--
Reply to this email directly or view it on GitHub:
One question: what is the correct: altering via Geany Tools, ... or editing
directly in the file /usr/share/geany/file...
Because opening in Tools, **all lines appear commented** and is is different
from the same file in /usr/share/geany/file...
What is actually used ?
--
Reply to this email
The bad news is that it doesn't work too.
I have added it, closed geany, reopen and all is the same.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3860#issuecomment-2081480908
You are receiving this because you are subscribed to this thread.
Message
PHP uses "preprocessor" color for the dollar variables, not identifier_1 ( that
sh/bash uses )
**The question is:** Why geany can draw php dollar variables interpolated in
string correctly, but not for shellscript ?
--
Reply to this email directly or view it on GitHub:
An important observation:
For single quoted string 'Single quoted string kills $dollar $vars' it is OK as
they kill dollar variables. In this case, the string color is used.
But double quotes "Double quotation keeps the $dollar $variables" they should
be colored as identifier_1 as geany does
I thank the lexer.bash.styling.inside.string information. How to set it ?
If Geany color application followed a simple rule, it would NOT depend on
language neither of this config.
The algorithm now paits string after the identifier_1 color with is for dollar
variables.
If just the identifier_1
I use vim and it always color the identifier with a different color. It
does not matter if is shell script or php.
If geany draws identifier_1 nicely out of the string and do not when the
dollar variable is interpolated in a string it is geany weakness and I
could myself show how to fix it
Em
An identifier inside a string should be colored as identifier, not as string.
Probably it's related to the execution order applying the colors.
Now the string scheme has more importance than identifier, and it should be
the opposite.
An example:
`"Here is a $variable is inside a string"`
Desire behavior is:
1- Add an empty line with one indentation
2- Put the } one line below this line at direcition of IF
3- Back the cursor at the blank line above, at indentation code.
--
Reply to this email directly or view it on GitHub:
new information:
if I open the if with the open and close bracks, could geany put the closing at
the correct place? So it is a feature request. Type:
if ( true) {}
Back the cursor 1 char, to be between the curly braces and press ENTER.
--
Reply to this email directly or view it on
I can not reproduce it anymore, please remove the topic untill I can reproduce,
and I will recreate. I saw the bug once but I can not reprocuce right now.
Please delete the topic. Tks
--
Reply to this email directly or view it on GitHub:
If I write an "if" in javascript that use curly braces, the behavior of Geany
if fine, as it closes the curly brace exactly in the direction of the opening
if. BUT when I do this in PHP file, the closing curly brace is put one TAB to
right, forcing the user to delete the extra TAB. Should be
The tool to comment/uncomment Lines could be more elegant, adding all the # to
the BEGINNING of lines!
And I saw a bug, it failing today, couldn't uncomment had to use REPLACE tool.
Works well to comment, but to uncomment, FAILED.
My suggestion is like this:
Nowadays|
> It is inappropriate to abuse anybody contributing to any project no matter
> what their status in the project. An opinion is a personal position based on
> the contributors experience, just because that does not agree with your
> personal opinion is not an excuse for abuse.
>
> If you had
Even Microsoft Code uses this behavior. I found abusive you saying that this
feature may not be important or useful.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3546#issuecomment-1689218495
You are receiving this because you are subscribed to
It seems you didn't understand the point.
The example of a shor autocomplete with 6 items is when you type part of a
VARIABLE NAME that you are creating.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3546#issuecomment-1689159714
You are receiving
How old are you? I program since the year 2000 and all you post is negative,
shows bad will.
NETBEANS USES THIS BEHAVIOR, so I don't think Netbeans developers had a less
inteligent decision.
--
Reply to this email directly or view it on GitHub:
Every good editor has this behaviour, for instance Netbeans.
Supose you have 5 itens in autocomplete. with one key press you can reach the
last or 5 hits, what is more efficient?
If we go to the LAST you can return to the first, only press DOWN as it will
wraps again the boundary, to first.
When autocomplete list opens, sometimes is faster go to the last item moving UP
instead of rolling all itens to down...
It you are at the first and moves up, I think that it should go to the LAST
item (as a cicle)
--
Reply to this email directly or view it on GitHub:
27 matches
Mail list logo
