Re: [Geany-Users] Highlight C function names?

[Lex Trotman]

On 11 January 2014 13:21, Nate Bargmann  wrote:

> As I use Geany for C work, one enhancement to the syntax highlighting
> would be to have C function names highlighted.  This would be any
> symbol, other than a C language keyword such as do, if, else, while,
> etc. that often have an open parenthesis following them and are already
> highlighted.
>
> For example, main() would have the word "main" highlighted but not the
> paratheses.  Or, foo(bar(a, (b * x))) would have the words "foo" and "bar"
> highlighted, and the parentheses, operators, and arguments would be in
> the current colors.
>
> Perhaps this is a limitation of the Scintilla editor?
>

You are correct that the first step would be to make Scintilla's C lexer
identify function calls as separate entities that can be highlighted. (and
an option to turn this off as well)

Cheers
Lex


>
> This would really help when dealing with source that uses libraries such
> as Gtk+ with many long function names on line after line.
>
> Thanks!
>
> - Nate
>
> --
>
> "The optimist proclaims that we live in the best of all
> possible worlds.  The pessimist fears this is true."
>
> Ham radio, Linux, bikes, and more: http://www.n0nb.us
> ___
> Users mailing list
> Users@lists.geany.org
> https://lists.geany.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.geany.org
https://lists.geany.org/cgi-bin/mailman/listinfo/users

[Geany-Users] Highlight C function names?

[Nate Bargmann]

As I use Geany for C work, one enhancement to the syntax highlighting
would be to have C function names highlighted.  This would be any
symbol, other than a C language keyword such as do, if, else, while,
etc. that often have an open parenthesis following them and are already
highlighted.

For example, main() would have the word "main" highlighted but not the
paratheses.  Or, foo(bar(a, (b * x))) would have the words "foo" and "bar"
highlighted, and the parentheses, operators, and arguments would be in
the current colors.

Perhaps this is a limitation of the Scintilla editor?

This would really help when dealing with source that uses libraries such
as Gtk+ with many long function names on line after line.

Thanks!

- Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us
___
Users mailing list
Users@lists.geany.org
https://lists.geany.org/cgi-bin/mailman/listinfo/users

Re: [Geany-Users] document_open_file(already_open) makes it most recent

[Thomas Martitz]

Am 10.01.2014 20:57, schrieb Lex Trotman:




On 11 January 2014 05:27, Dimitar Zhekov > wrote:


Hi,

Currently, any attempt to open a file which is already open moves it
to the top of the Recent list. So, if you switch to a open file from
a compiler message or a FiF match, it that file becomes the most
recent. However, Find in Session displays basename:line matches, but
selecting a file does not affect Recent.

Should "opening" an open file move it to the top of recent?
If so, shoudn't clicking a Find in Session match move the file too?


Hi Dimitar,

Yes its inconsistent.

In addition to the cases you mention, when files are opened from the 
previous session they are not moved to the top/added to the MRU list. 
 So files that are open for a while fall off the list.  This is very 
annoying when you accidently close them and then try to re-open them.


IMHO the MRU list should be a real Most Recently **USED** list, ie 
files go to the top when they are focussed for any reason.



I think my splitwindow2 work might fix this. Part of the changes is 
update the MRU whenever the focus changes.


Best regards.


___
Users mailing list
Users@lists.geany.org
https://lists.geany.org/cgi-bin/mailman/listinfo/users

Re: [Geany-Users] document_open_file(already_open) makes it most recent

[Lex Trotman]

On 11 January 2014 05:27, Dimitar Zhekov  wrote:

> Hi,
>
> Currently, any attempt to open a file which is already open moves it
> to the top of the Recent list. So, if you switch to a open file from
> a compiler message or a FiF match, it that file becomes the most
> recent. However, Find in Session displays basename:line matches, but
> selecting a file does not affect Recent.
>
> Should "opening" an open file move it to the top of recent?
> If so, shoudn't clicking a Find in Session match move the file too?
>

Hi Dimitar,

Yes its inconsistent.

In addition to the cases you mention, when files are opened from the
previous session they are not moved to the top/added to the MRU list.  So
files that are open for a while fall off the list.  This is very annoying
when you accidently close them and then try to re-open them.

IMHO the MRU list should be a real Most Recently **USED** list, ie files go
to the top when they are focussed for any reason.

Cheers
Lex

>
> --
> E-gards: Jimmy
> ___
> Users mailing list
> Users@lists.geany.org
> https://lists.geany.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.geany.org
https://lists.geany.org/cgi-bin/mailman/listinfo/users

[Geany-Users] document_open_file(already_open) makes it most recent

[Dimitar Zhekov]

Hi,

Currently, any attempt to open a file which is already open moves it
to the top of the Recent list. So, if you switch to a open file from
a compiler message or a FiF match, it that file becomes the most
recent. However, Find in Session displays basename:line matches, but
selecting a file does not affect Recent.

Should "opening" an open file move it to the top of recent?
If so, shoudn't clicking a Find in Session match move the file too?

-- 
E-gards: Jimmy
___
Users mailing list
Users@lists.geany.org
https://lists.geany.org/cgi-bin/mailman/listinfo/users