A convenient Vala syntax sugar is like this:
```vala
class TheNameSpace.ASubNameSpace.SomeKindOfThing
{
// ...
}
```
It's equivalent to:
```vala
namespace TheNameSpace {
namespace ASubNameSpace {
class SomeKindOfThing {
// ...
}
}
}
```
But this seems to break type name highlighting. Presumably it's a bug in the ctags/tagmanager parsing.
--
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/1707
Suggest adding these to the list of css3 properties. Specifically:
grid grid-area grid-auto-columns grid-auto-flow grid-auto-rows grid-column grid-column-end grid-column-gap grid-column-start grid-gap grid-row grid-row-end grid-row-gap grid-row-start grid-template grid-template-areas grid-template-columns grid-template-rows
--
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/1705
I use large fonts & long file names. If I get more than 2 tabs I can't tell what files are in what tab. If I get more than 3 some aren't even visible, let alone identifiable. Any of the following 3 things would improve Geany a lot for people like me. In order of preference:
1. A drop down menu showing the full path/name for each open file, allowing the width to go all the way across the monitor. Click on an item and that file becomes the focused tab. Actually with this you wouldn't even need the tab bar & it would be nice if we could turn it off.
and/or
2. A command line option that causes the file to be opened in a new window.
and/or
3. When right clicking on a tab and selecting "open in new window", the tab in the first window would close.
People who don't use something like the Openbox native menus may not see why I consider these multi-window options as acceptable substitutes for a drop down menu. That's because separate windows are automatically put on a drop down menu when using the OB native menus, kind of like task bar, but way better.
--
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/1700
Hi,
I wanted to try running geany from source,
so an `autogen.sh` and `make` later I've got it.
I run `src/geany`, skipping `make install` since I don't want to install it,
it gives me the error Failed to open file '/usr/local/share/geany/geany.glade'.
I look around and find no option or environment variable to change the data directory, (something like `-c`)
The two options I found were:
* `mkdir build && ./configure --prefix=$(pwd)/build && make && make install`
* changing in https://github.com/geany/geany/blob/master/src/utils.c#L2142 `GEANY_DATADIR` to `""`
neither are good.
Is there something to do to use a source version of geany that doesn't requires modifying the source code or installing it after each make?
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/788
related to this old issue: https://github.com/geany/geany/issues/788
I have stated my rationale there, repeating here:
--------------------------------------------------------------------------------------
dear all, this original post really is about a not so well thought design of geany. I want to tell you a bit specific sitation. I am running Geany on my phone (Ubuntu Touch), you can see here: neither it does on other Linux machines by default
Now, on the phone, the most of the filesystem except ~/, is read-only. Also, is very limitted in space. Installing geany's files into /usr or anywhere outside of ~/ would be considered very expensive. So me, I installed it locally under my home. Should geany be a bit more flexible, that'd be not a problem at all. Even desktop launcher can be added to ~/.local/usr/share/applications/ instead of /usr/share/applications, and so on, HOWEVER, I had to manually ln -s my home based installation back to /usr/share/geany.
Sure, I can do this, just as I can install with a prefix to my home, but that is not convenient. That is not allowing for there to be a way of convenient automated installation to user's home directory. And basically, the ONLY portion which makes it hard, is that path containing the glider.
Just imagine how much more flexible and convenient the Geany would become if you could simply supply the path via environmental var or a command line switch.
Again, I can help myself, but I wanted to point out that in deed, Geany has a small part that limits it without clear reason for it to be that way.
Best Regards,
Kris
--
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/1702