>From @b4n's post I would say its a bit of both.
--
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/1249#issuecomment-374051508
@elextr: Ahh OK, got it, thanks. Is this in Geany itself or ctags?
--
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/1249#issuecomment-374050813
Nup, exactly the same. Copy the example above, delete the ( after f and
re-type it.
Note that if you have any other files open that have a function called `f` it
will show those in the calltip instead, but thats a different imbecility.
--
You are receiving this because you are subscribed to t
ConEmu does not appear to be a GTK widget and therefore can't be embedded into
a GTK application like Geany.
--
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/675#issuecomment-374045523
@osevoso that might be suitable if it's written in native code and uses
standard C/C++ that can be compiled on non-MSVC compilers and non-Windows OS
(the nightly builds are cross-compiled).
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view
Closed #1290.
--
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/1290#event-1527380016
What about a ConEmu as embedded term, like it is done in the Git Extention
project?
Here is an example of this: https://github.com/gitextensions/conemu-inside
Has anyone considered this option? There is no FAR required.
--
You are receiving this because you are subscribed to this thread.
Repl
Has this been fixed? Can't re-produce it but maybe I'm doing something wrong.
--
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/1249#issuecomment-374000665
@benubird: do you still have this issue with the actual 1.33 versions of Geany
and Geany-Plugins?
--
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/1262#issuecomment-374000222
IMHO this can be closed.
--
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/1290#issuecomment-37481
@YuriPetrov: did this problem occur again in the meantime or can this issue be
closed?
--
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/1341#issuecomment-373999243
```box-sizing``` is in the list of CSS3 properties and the others mentioned
like ```margin```, ```padding``` are CSS1 properties.
CSS1 and CSS2 properties by intention have a different color than CSS3
properties, see this example:
![geany-css-example](https://user-images.githubusercontent.com/9
I don't know about Perl, but in many languages a file is not a scope, so
"unknown" is more correct, and in other languages the scope is a module or
package name that derives from the filename, eg Java and in others its derived
from the path eg Python. So unless someone is going to make the mess
I agree with @LarsGit223, will close this in a week unless somebody objects.
--
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/1484#issuecomment-373994325
Sorry, but I voted for not changing this.
IMHO the scope shows the context inside of the file. And the filename is
already shown in the title of the tab. So I think it shouldn't be duplicated in
the scope field.
--
You are receiving this because you are subscribed to this thread.
Reply to th
> I think what's a bit inconsistent is, that a user can open as many empty
> untitled documents as he/she wants if other, not empty documents are opened.
> But that's out of scope of this PR.
Opening lots of empty documents is not an encouraged use-case, so I wouldn't
worry. Unnamed documents
I agree too, would rather close #1539 as wontfix. Thanks for bringing this to
our attention and for your efforts on visiting old bug reports!
--
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/pul
I have done the announced changes. The behaviour should now be consistent. It
is not trying to open a new empty document if option ```-e``` was given and
```new_document_after_close``` is set to ```TRUE```. This prevents the
unnecessary message on startup in that case.
I noticed that we do get
I agree :+1:
--
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/pull/1810#issuecomment-373990576
@LarsGit223 pushed 2 commits.
fee8468 cli: do not try to open a new file on option '-e' if
'new_document_after_close' is TRUE
56068f9 cli: added documentation for new option '-e'
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://github.com/geany/
> I'm actually just trying to look at some open-issues
Yes, noticed and thank you for your efforts (we don't say that enough).
As is illustrated by the lack of a "won't fix" label Geany tends to not have
much of a hard reject philosophy, especially for enhancements. In general if
someone think
> unless you uncheck the option of course :)
Yes, it's really just a comfortability issue and I'm totally fine if the PR
would be rejected and having the issue closed as "won't fix" (or some other
label which is appropriate). I'm actually just trying to look at some
open-issues which I can fix
Thank you a lot!
I would try and fill this wiki page. After that, I'll close this one. It's all
must be well prepared.
So till that I'll be exercising on this page.
E.g. I have another remark on Geany's context :)
--
You are receiving this because you are subscribed to this thread.
Reply to thi
23 matches
Mail list logo
