![overwritemodeoncutandpaste](https://cloud.githubusercontent.com/assets/7548378/10828753/204e0a68-7e6e-11e5-83dd-68fd1f5ecb5f.png)
I put <b>aaaa</b> into the paste buffer from line 1
I put the cursor in overwrite mode - you can see it is horizontal not vertical
I pasted.
I expected to get line 3 because I was in overwrite mode, but instead I got line 2, which I can easily get if the cursor is in insert mode.
Please consider having paste in overwrite mode overwrite rather than insert as this would give the user even more capability.
Thanks!
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/716
I am not sure what you specifically call the reload banner but here is a screenshot, pointing to the issue:
![core py - -home-calum-projects-autoshutdown-autoshutdown - autoshutdown plugin - geany_036](https://cloud.githubusercontent.com/assets/606038/10635467/dfec3…
Overall I really happy that this banner was introduced and it was something I was hoping would be implemented. The problem I am finding is that at fullscreen the buttons are placed far too far away from any other part of the application and require significant extra mouse movement.
It might be that gtk constrains what is possible without writing a custom widget but what I would propose is that if possible place the buttons on the lefthand side.
I made a quick mockup on my proposal, also reducing the amount of vertical space the banner takes up:
![core py - -home-calum-projects-autoshutdown-autoshutdown - autoshutdown plugin - geany_0362](https://cloud.githubusercontent.com/assets/606038/10636591/a609…
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/706
As by discussion I'm going to close this PR without merging. Thanks for contributing, but it appears to don't improve documentation at this point.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/636#issuecomment-151614160
> @@ -40,8 +40,9 @@ GNU versions of these tools are recommended.
>
> Installation
> ------------
> -Installing Geany is done by the following three commands:
> -$ ./configure
> +Installing Geany is done by the following commands:
> +$ libtoolize
> +$ ./autogen.sh
I think it only re-runs `configure` script as needed, not re-generates it.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/636/files#r43080313
> @@ -40,8 +40,9 @@ GNU versions of these tools are recommended.
>
> Installation
> ------------
> -Installing Geany is done by the following three commands:
> -$ ./configure
> +Installing Geany is done by the following commands:
> +$ libtoolize
> +$ ./autogen.sh
I thought `make` did that if you edit any dependencies?
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/636/files#r43075012
> @@ -40,8 +40,9 @@ GNU versions of these tools are recommended.
>
> Installation
> ------------
> -Installing Geany is done by the following three commands:
> -$ ./configure
> +Installing Geany is done by the following commands:
> +$ libtoolize
> +$ ./autogen.sh
It needs to be called any time `configure` script needs to be re-generated also, like if someone edits `configure.ac` or any of the `.m4` files. I think that's why `autogen.sh` calls `configure` for you, to avoid the extra step.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/636/files#r43072142
> @@ -40,8 +40,9 @@ GNU versions of these tools are recommended.
>
> Installation
> ------------
> -Installing Geany is done by the following three commands:
> -$ ./configure
> +Installing Geany is done by the following commands:
> +$ libtoolize
It's called from inside `autogen.sh`, so yeah it shouldn't be needed to called explicitly.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/636/files#r43071859
> @@ -40,8 +40,9 @@ GNU versions of these tools are recommended.
>
> Installation
> ------------
> -Installing Geany is done by the following three commands:
> -$ ./configure
> +Installing Geany is done by the following commands:
> +$ libtoolize
> +$ ./autogen.sh
And `autogen.sh` is only needed first time after a new git clone, for tarballs or the second time only `./configure` is needed.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/636/files#r43067277
> @@ -40,8 +40,9 @@ GNU versions of these tools are recommended.
>
> Installation
> ------------
> -Installing Geany is done by the following three commands:
> -$ ./configure
> +Installing Geany is done by the following commands:
> +$ libtoolize
Why have put this explicit here? In about most cases its not needed from my experince
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/636/files#r43059170