[opensuse] konsole dictating dimensions of gvim window

toothpik

4 Jun 2015 4 Jun '15

00:34

I am running openSUSE v 13.1, konsole v 2.11.3, gvim v 7.4.729 if I start a gvim session from the konsole command line it assumes the same dimensions as konsole -- if I instead start gvim from the alt-F2 run starter it assumes whatever dimensions I have specified in my startup script, or it defaults to a cute 25 line by 80 column display can someone tell me how to end the tyranny of konsole sizing my gvim windows? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Show replies by date

Anton Aylward

4 Jun 4 Jun

00:51

On 06/03/2015 08:34 PM, toothpik wrote:

...

I am running openSUSE v 13.1, konsole v 2.11.3, gvim v 7.4.729

if I start a gvim session from the konsole command line it assumes the same dimensions as konsole -- if I instead start gvim from the alt-F2 run starter it assumes whatever dimensions I have specified in my startup script, or it defaults to a cute 25 line by 80 column display

Interesting. When i start up in those two modes I do get different sized windows but neither is particularly large, certainly not the the same dimensions as the konsole. I'm running 13.1 (64bit) Repository: KDE_Current Name: konsole Version: 4.14.3-1.4 Repository: openSUSE-13.1-Update Name: gvim Version: 7.4.052-4.1 *WHAT* *STARRTUP* *SCRIPT* ??? ~/.viminfo ~/.vimrc ~/.gvimrc or something in the ~/vim/ directory that might examine context. And lets not forget the globals. A quick RTFM tells me about /usr/share/vim/vim74/syntax/syntax.vim System wide syntax initializations. /usr/share/vim/vim74/syntax/syntax.vim System wide syntax initializations. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

toothpik

01:39

On Wed, Jun 03, 2015 at 08:51:25PM -0400, Anton Aylward wrote:

...

On 06/03/2015 08:34 PM, toothpik wrote:

...
I am running openSUSE v 13.1, konsole v 2.11.3, gvim v 7.4.729

if I start a gvim session from the konsole command line it assumes the same dimensions as konsole -- if I instead start gvim from the alt-F2 run starter it assumes whatever dimensions I have specified in my startup script, or it defaults to a cute 25 line by 80 column display

...

Interesting. When i start up in those two modes I do get different sized windows but neither is particularly large, certainly not the the same dimensions as the konsole.

...

I'm running 13.1 (64bit)

...

Repository: KDE_Current Name: konsole Version: 4.14.3-1.4

...

Repository: openSUSE-13.1-Update Name: gvim Version: 7.4.052-4.1

...

*WHAT* *STARRTUP* *SCRIPT* ???

I have bash scripts that start gvim with for example option -c 'source ~/.vim/plan.vim' and in plan.vim I'll define various leader mappings, autocommands, specialized register contents, and if has('gui_running') I'll set lines and columns (with a winsize command) to my prefered size -- all for my "plan" application my request for my winsize is honored if I use alt-F2 to run the bash starter script, but if I run it from konsole the gvim window is as big as the konsole -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Anton Aylward

04:50

On 06/03/2015 09:39 PM, toothpick wrote:

...

I have bash scripts that start gvim with for example option

It would have been nice if you'd mentioned this to start with and how you used those options in the different contexts. * You might also research to see what other initializations files are * * executed. * When I read the various ones I have I see that I can set window size and position according to the type of file I'm editing without the need for the kind of command line option you use, just by making use of file name suffices and/or MIME type. No need to anything extra on the command line! You might also look into that. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

toothpik

12:08

On Thu, Jun 04, 2015 at 12:50:53AM -0400, Anton Aylward wrote:

...

On 06/03/2015 09:39 PM, toothpick wrote:

...
I have bash scripts that start gvim with for example option

...

It would have been nice if you'd mentioned this to start with and how you used those options in the different contexts.

but -- it's kind of irrelevant

...

* You might also research to see what other initializations files are * * executed. *

the resizing is not coming from any initialization file mentioned in :scriptnames as I said, it's coming from the fact that I start the gvim session from a konsole command line, as evidenced from the fact that it doesn't happen when I start gvim from the alt-F2 run starter this is either konsole, or kdm, or kde taking liberties with my window management

...

When I read the various ones I have I see that I can set window size and position according to the type of file I'm editing without the need for the kind of command line option you use, just by making use of file name suffices and/or MIME type.

...

No need to anything extra on the command line!

...

You might also look into that.

yes, thank you -- you've been most helpful -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Linda Walsh

6 Jun 6 Jun

01:04

New subject: [opensuse] Re: konsole dictating dimensions of gvim window

toothpik wrote:

...

my request for my winsize is honored if I use alt-F2 to run the bash starter script, but if I run it from konsole the gvim window is as big as the konsole

That is a **feature**. It gives you the same size window as if you brought up 'vim'. It is trying to be consistent. If people worked with 100char wide terms, all the time, then having gvim coming up with 65chars wide would be inconsistent with other ways of invoking vim.. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

toothpik

08:58

New subject: [opensuse] Re: konsole dictating dimensions of gvim window

On Fri, Jun 05, 2015 at 06:04:02PM -0700, Linda Walsh wrote:

...

toothpik wrote:

...

...
my request for my winsize is honored if I use alt-F2 to run the bash starter script, but if I run it from konsole the gvim window is as big as the konsole

...

That is a **feature**.

if that's true it's a feature I'd like to know how to turn off

...

It gives you the same size window as if you brought up 'vim'. It is trying to be consistent.

...

If people worked with 100char wide terms, all the time, then having gvim coming up with 65chars wide would be inconsistent with other ways of invoking vim..

it does seem intentional -- when I make konsole tiny, my plan script brings up a tiny plan window how in heck do I regain control of my window size? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Linda Walsh

16:34

New subject: [opensuse] Re: konsole dictating dimensions of gvim window

toothpik wrote:

...

On Fri, Jun 05, 2015 at 06:04:02PM -0700, Linda Walsh wrote:

...
toothpik wrote:

...
...
my request for my winsize is honored if I use alt-F2 to run the bash starter script, but if I run it from konsole the gvim window is as big as the konsole

...
That is a **feature**.

if that's true it's a feature I'd like to know how to turn off

how in heck do I regain control of my window size?

--- You have control by choosing whatever size your Terminal window is. Either that, or in your .gvimrc let &columns = 80 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrei Borzenkov

17:09

New subject: [opensuse] Re: konsole dictating dimensions of gvim window

В Sat, 06 Jun 2015 09:34:50 -0700 Linda Walsh пишет:

...

toothpik wrote:

...
On Fri, Jun 05, 2015 at 06:04:02PM -0700, Linda Walsh wrote:

...
toothpik wrote:

...
...
my request for my winsize is honored if I use alt-F2 to run the bash starter script, but if I run it from konsole the gvim window is as big as the konsole

...
That is a **feature**.

if that's true it's a feature I'd like to know how to turn off

how in heck do I regain control of my window size?

--- You have control by choosing whatever size your Terminal window is. Either that, or in your .gvimrc

let &columns = 80

Default size for gvim window can also be set in Xresources. It is extensively documented in vim help. Including the fact that parent terminal size is the default :) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

toothpik

7 Jun 7 Jun

01:57

New subject: [opensuse] Re: konsole dictating dimensions of gvim window

On Sat, Jun 06, 2015 at 08:09:26PM +0300, Andrei Borzenkov wrote:

...

В Sat, 06 Jun 2015 09:34:50 -0700 Linda Walsh пишет:

...

...
toothpik wrote:

...
On Fri, Jun 05, 2015 at 06:04:02PM -0700, Linda Walsh wrote:

...
toothpik wrote:

...
...
my request for my winsize is honored if I use alt-F2 to run the bash starter script, but if I run it from konsole the gvim window is as big as the konsole

...
That is a **feature**.

if that's true it's a feature I'd like to know how to turn off

how in heck do I regain control of my window size?

...

Default size for gvim window can also be set in Xresources. It is extensively documented in vim help. Including the fact that parent terminal size is the default :)

wow for a brief moment I suffered a spasm of optimism there really is an answer to this -- it sounds spot on what my issue is but if the "extensive documentation" you are referring to is the little taste of info under :h xterm-resize which appears to directly address my issue, and when the magic line XTerm*allowWindowOps: true is added to ~/.Xresources and a xrdb -merge ~/.Xresources is performed, then xrdb -query shows the new setting tucked away amongst all the other settings, one could justifiably feel it is fixed -- until he tries it and the window still refuses to assume the size requested in the script (exasperatingly honoring the column setting but not the lines) thank you Andrei, but this didn't give me back control of my gvim window size (when the starter script is run from konsole) -- is there really more help elsewhere I've failed to find? is there a reboot necessary? do I have to do the xrdb -merge under a full moon? (we're only 4 days after the full moon -- doesn't that count?) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrei Borzenkov

04:15

New subject: [opensuse] Re: konsole dictating dimensions of gvim window

В Sat, 6 Jun 2015 20:57:02 -0500 toothpik пишет:

...

On Sat, Jun 06, 2015 at 08:09:26PM +0300, Andrei Borzenkov wrote:

...
В Sat, 06 Jun 2015 09:34:50 -0700 Linda Walsh пишет:

...
...
toothpik wrote:

...
On Fri, Jun 05, 2015 at 06:04:02PM -0700, Linda Walsh wrote:

...
toothpik wrote:

...
...
my request for my winsize is honored if I use alt-F2 to run the bash starter script, but if I run it from konsole the gvim window is as big as the konsole

...
That is a **feature**.

if that's true it's a feature I'd like to know how to turn off

how in heck do I regain control of my window size?

...
Default size for gvim window can also be set in Xresources. It is extensively documented in vim help. Including the fact that parent terminal size is the default :)

wow for a brief moment I suffered a spasm of optimism there really is an answer to this -- it sounds spot on what my issue is

but if the "extensive documentation" you are referring to is the little taste of info under

:h xterm-resize

which appears to directly address my issue, and when the magic line

XTerm*allowWindowOps: true

is added to ~/.Xresources and a

xrdb -merge ~/.Xresources

is performed, then

xrdb -query

shows the new setting tucked away amongst all the other settings, one could justifiably feel it is fixed -- until he tries it and the window still refuses to assume the size requested in the script (exasperatingly honoring the column setting but not the lines)

thank you Andrei, but this didn't give me back control of my gvim window size (when the starter script is run from konsole) -- is there really more help elsewhere I've failed to find?

I'd start with http://vimdoc.sourceforge.net/htmldoc/gui_x11.html#gui-resources or vim -c ":help gui_x11"

...

is there a reboot necessary? do I have to do the xrdb -merge under a full moon? (we're only 4 days after the full moon -- doesn't that count?)

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

toothpik

09:27

New subject: [opensuse] Re: konsole dictating dimensions of gvim window

On Sun, Jun 07, 2015 at 07:15:29AM +0300, Andrei Borzenkov wrote:

...

В Sat, 6 Jun 2015 20:57:02 -0500 toothpik пишет:

...

...
On Sat, Jun 06, 2015 at 08:09:26PM +0300, Andrei Borzenkov wrote:

...
В Sat, 06 Jun 2015 09:34:50 -0700 Linda Walsh пишет:

...
...
toothpik wrote:

...
On Fri, Jun 05, 2015 at 06:04:02PM -0700, Linda Walsh wrote:

...
toothpik wrote:

...
> my request for my winsize is honored if I use alt-F2 to run the bash > starter script, but if I run it from konsole the gvim window is as big > as the konsole ----

...
That is a **feature**.

if that's true it's a feature I'd like to know how to turn off

how in heck do I regain control of my window size?

...
Default size for gvim window can also be set in Xresources. It is extensively documented in vim help. Including the fact that parent terminal size is the default :)

wow for a brief moment I suffered a spasm of optimism there really is an answer to this -- it sounds spot on what my issue is

but if the "extensive documentation" you are referring to is the little taste of info under

:h xterm-resize

which appears to directly address my issue, and when the magic line

XTerm*allowWindowOps: true

is added to ~/.Xresources and a

xrdb -merge ~/.Xresources

is performed, then

xrdb -query

shows the new setting tucked away amongst all the other settings, one could justifiably feel it is fixed -- until he tries it and the window still refuses to assume the size requested in the script (exasperatingly honoring the column setting but not the lines)

thank you Andrei, but this didn't give me back control of my gvim window size (when the starter script is run from konsole) -- is there really more help elsewhere I've failed to find?

...

I'd start with

...

http://vimdoc.sourceforge.net/htmldoc/gui_x11.html#gui-resources

...

or

...

vim -c ":help gui_x11"

wow who knew you can get quality vim help on the opensuse list! thank you Andrei, you've brought some sanity into my life there is no mention of the -geometry option in all of :h starting or :h 'lines' (which does have an irrelevant posix rabbit hole you can fall down) I was so sure this was a KDM buggaboo I asked here hats off to Andrei and the opensuse list! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Patrick Shanahan

4 Jun 4 Jun

01:00

* toothpik [06-03-15 20:38]:

...

I am running openSUSE v 13.1, konsole v 2.11.3, gvim v 7.4.729

if I start a gvim session from the konsole command line it assumes the same dimensions as konsole -- if I instead start gvim from the alt-F2 run starter it assumes whatever dimensions I have specified in my startup script, or it defaults to a cute 25 line by 80 column display

can someone tell me how to end the tyranny of konsole sizing my gvim windows?

It's not "tyranny", but your setting for terminal windows. Go to systemsettings and configure the terminal window and size you desire. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Patrick Shanahan

01:13

* Patrick Shanahan [06-03-15 21:03]:

...

* toothpik [06-03-15 20:38]:

...
I am running openSUSE v 13.1, konsole v 2.11.3, gvim v 7.4.729

if I start a gvim session from the konsole command line it assumes the same dimensions as konsole -- if I instead start gvim from the alt-F2 run starter it assumes whatever dimensions I have specified in my startup script, or it defaults to a cute 25 line by 80 column display

can someone tell me how to end the tyranny of konsole sizing my gvim windows?

It's not "tyranny", but your setting for terminal windows. Go to systemsettings and configure the terminal window and size you desire.

You will find it: configure desktop -> default applications -> terminal emulator if you have it set to konsole, that is what will try to run and it will use the setting as it is configured. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

toothpik

01:42

On Wed, Jun 03, 2015 at 09:13:16PM -0400, Patrick Shanahan wrote:

...

* Patrick Shanahan [06-03-15 21:03]:

...
* toothpik [06-03-15 20:38]:

...
I am running openSUSE v 13.1, konsole v 2.11.3, gvim v 7.4.729

if I start a gvim session from the konsole command line it assumes the same dimensions as konsole -- if I instead start gvim from the alt-F2 run starter it assumes whatever dimensions I have specified in my startup script, or it defaults to a cute 25 line by 80 column display

can someone tell me how to end the tyranny of konsole sizing my gvim windows?

It's not "tyranny", but your setting for terminal windows. Go to systemsettings and configure the terminal window and size you desire.

...

You will find it: configure desktop -> default applications -> terminal emulator

...

if you have it set to konsole, that is what will try to run and it will use the setting as it is configured.

no, the only thing there is how to tell KDE I want to use konsole as my terminal emulator (as opposed to xterm or whatever), and there are no settings there for the emulator chosen it IS a tyranny of size imposed by konsole on my gvim window -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

I. Petrov

01:55

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, Set the initial gvim window size in ~/.gvimrc e.g. set lines=25 set columns=80 and start gvim again from the konsole. Regards, I. Petrov On Wed, 3 Jun 2015, toothpik wrote:

...

I am running openSUSE v 13.1, konsole v 2.11.3, gvim v 7.4.729

if I start a gvim session from the konsole command line it assumes the same dimensions as konsole -- if I instead start gvim from the alt-F2 run starter it assumes whatever dimensions I have specified in my startup script, or it defaults to a cute 25 line by 80 column display

can someone tell me how to end the tyranny of konsole sizing my gvim windows? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Signed by Topal iQIcBAEBAgAGBQJVb7AJAAoJEH8sJoKRFRU5UOYP+wQcXBR30VsvWt2r11lTW3P3 L8n9panYG+v/R/laL4IlQmsspNWEPj7aSj6pZ4o/BN+LxG4RD/NEKLeMIyf/JoNY XcO4RfuE3xrjHSNaq7HsmM8u5yDC7G0F11dt6hVOV3Eu/ZvJm4A49UrmFrCfabWw lD4nCxROzUnDZ0i8YCcPuDYMTJ57jaQNtkAw9KQcWGdLhIjsrio02pT9r2/zGJgv Bwt8td74M1OjBels2JfsWj4mf2AhkSKpnkHopLfhsvx5MWtX6hamjiBaXLl5Mu76 /QBR1SgBhyxuz2JMU+DLx3WBzKnbMAUUTDnTZ9QZcO3lNqRiniLsS7epjkKtR6JW cxvPcz2NLmRcfdU82EQXqqxlmwZ07pzccXRk8xIS5xqjbk57PV6XwM1UV8APrpZ2 3QrWz1MKb6oY8mlj2ouHhE6tFfFhEhCnp5bBeW2qgNVKNw1ryxI3Cq0ISF9tg7hW rOUoQ1RvQLdca4fFoRLxx8tXCjGIm6HSTtmaYKvMgngcXqDlYSm8nEUYl3jJqYb9 7C7Ws389EYtPfWhNzbFpYECWp0Sy73cux3JgWdbVyxog4bXa1aDJC4UVfWaIEtFM 4gWSvMJA8JZe56J4zhNF3eUxxbzfxDt5pN2zA++dVeIn636Opd8MeWJTT5vL3jk2 fYhrku3kgwRpviJbexkl =qrEF -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

toothpik

04:16

...

On Wed, 3 Jun 2015, toothpik wrote:

...

...
I am running openSUSE v 13.1, konsole v 2.11.3, gvim v 7.4.729

if I start a gvim session from the konsole command line it assumes the same dimensions as konsole -- if I instead start gvim from the alt-F2 run starter it assumes whatever dimensions I have specified in my startup script, or it defaults to a cute 25 line by 80 column display

can someone tell me how to end the tyranny of konsole sizing my gvim windows? -- On Thu, Jun 04, 2015 at 04:55:18AM +0300, I. Petrov wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

...

Hello,

...

Set the initial gvim window size in ~/.gvimrc e.g.

...

set lines=25 set columns=80

...

and start gvim again from the konsole.

thanx but no thanx -- I don't want the plan dimensions for all gvim windows, I want them when I am editing the plan, and only when I am editing the plan -- that's why I put the dang winsize command in ~/.vim/plan.vim and why I edit the plan with the gvim -c 'source ~/.vim/plan.vim' plan_2015 command -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

David Haller

09:41

Hello, On Wed, 03 Jun 2015, toothpik wrote:

...

gvim -c 'source ~/.vim/plan.vim' plan_2015

Try: LINES= COLUMNS= gvim -c 'source ~/.vim/plan.vim' plan_2015 HTH, -dnh -- Memory fault -- core...uh...um...core... Oh dammit, I forget! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

toothpik

21:31

On Thu, Jun 04, 2015 at 11:41:02AM +0200, David Haller wrote:

...

Hello,

...

On Wed, 03 Jun 2015, toothpik wrote:

...
gvim -c 'source ~/.vim/plan.vim' plan_2015

...

Try: LINES= COLUMNS= gvim -c 'source ~/.vim/plan.vim' plan_2015

hmph -- I didn't know bash defined those -- but undefining them didn't make a difference -- it still came up huge for the nonce I'm going to train myself to always start the plan from the alt-F2 run starter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

I. Petrov

21:31

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, OK then. I've made a few tests and it seems that the if has('gui_running') statement does not detect the GUI properly every time (don't know why ... a race condition?). The execution of the source file however can be delayed by adding e.g. sleep 250m at the top of it. The value of 250 miliseconds seems to be enough (at least on my machine) in order the GUI to be detected every time and the code in the if has('gui_runing') statement to be executed. Also have in mind that the winsize command is obsolete and is recommended the set lines= and set columns= to be used. Hope that this what you are lookinng for. Regards, I. Petrov On Wed, 3 Jun 2015, toothpik wrote:

...

...
On Wed, 3 Jun 2015, toothpik wrote:

...
...
I am running openSUSE v 13.1, konsole v 2.11.3, gvim v 7.4.729

if I start a gvim session from the konsole command line it assumes the same dimensions as konsole -- if I instead start gvim from the alt-F2 run starter it assumes whatever dimensions I have specified in my startup script, or it defaults to a cute 25 line by 80 column display

can someone tell me how to end the tyranny of konsole sizing my gvim windows? -- On Thu, Jun 04, 2015 at 04:55:18AM +0300, I. Petrov wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

...
Hello,

...
Set the initial gvim window size in ~/.gvimrc e.g.

...
set lines=25 set columns=80

...
and start gvim again from the konsole.

thanx but no thanx -- I don't want the plan dimensions for all gvim windows, I want them when I am editing the plan, and only when I am editing the plan -- that's why I put the dang winsize command in ~/.vim/plan.vim and why I edit the plan with the

gvim -c 'source ~/.vim/plan.vim' plan_2015

command

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Signed by Topal iQIcBAEBAgAGBQJVcMOlAAoJEH8sJoKRFRU5tZwP/iH53GX5KAOb+OXYvQw+XbhF srZ+uhhMu9RkqhlMNM/8iAxNwAqGwe7FtXObTXSyS1qI2FOt53h23+PfvJCl5Woh VeRGxAobNVmSffCGAlvl5fGNfTrZmgA8iZNnGSKkrIpQKgJX1r6ntetqr9CUyg8d pnal0WahpCCSuGPIQRBJ151BBn+zfVA6ENO0COW/qWXj/rNFqbwAABLu4HXBJ0Kp NodFyYyqA9GjiUUJTBAoJ1dSorb+Dz1EzWD1A0zHrBlOiX8Wr/iLoHk3Dvc3JXii 9QC+DUjOWW3bvhuSql1GPCZk6QHcHvBxjRh+OtTWCU9VE1N54xZiCeMyADHpzyOn oXaLoyLgPYn95P90gZSiIAueeHVhYqAaS3TElY1vtGlnnRr6CK1XCegx9rSOWXtr 8tJeDXG192UOgUQ0TBUwe3br/fVZn8dRSCJ7jjzGUto4I6rQh7HWB21I9eoZ4ohm nGYK6aDO6k44XsffhutpsluJh2YlL7ASnGolKEs9CNNsvABx8BGrXfJ1kg8OsOx3 Fiu2YJQ6VdLtN9xWt6EAfaCXIn6KIpi3i5+E4dDWEr53LY/jiEGejD6kpxQ4HYk+ yQ9I9phjVP+emeCL85M0zVd5TZgWZmXXo9cfWLX6sUGGdGIDAPYFtNGYh5mIznum 3gzOr38lEHwLZAj43POr =LuO/ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Anton Aylward

21:43

On 06/03/2015 08:34 PM, toothpik wrote:

...

I am running openSUSE v 13.1, konsole v 2.11.3, gvim v 7.4.729

if I start a gvim session from the konsole command line it assumes the same dimensions as konsole -- if I instead start gvim from the alt-F2 run starter it assumes whatever dimensions I have specified in my startup script, or it defaults to a cute 25 line by 80 column display

can someone tell me how to end the tyranny of konsole sizing my gvim windows?

I wonder if you have aliasing vis 'search' going on. if i use 'gvim' i get small windows, but different positions for each of your two use cases. but if in the xterm of the konsole window I run 'vim' or 'vi' it appears as you describe, the complete window. When I run 'alias' I don't see anything to do with vim or gvim or vi Please don't get confused between bash's 'alias' and the email alias mechanism. There is also 'alternatives'. I don't have any set up for vim, gvim or vi anton@Mainbox:~> which gvim /usr/bin/gvim anton@Mainbox:~> which vim /usr/bin/vim anton@Mainbox:~> which vi /usr/bin/vi anton@Mainbox:~> ls -l /usr/bin/gvim /usr/bin/vim /usr/bin/vi /bin/vim -rwxr-xr-x 1 root root 2396872 Apr 3 2014 /bin/vim -rwxr-xr-x 1 root root 2648040 Apr 3 2014 /usr/bin/gvim lrwxrwxrwx 1 root root 8 Jul 11 2014 /usr/bin/vi -> /bin/vim lrwxrwxrwx 1 root root 8 Jul 11 2014 /usr/bin/vim -> /bin/vim -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

toothpik

5 Jun 5 Jun

17:43

On Thu, Jun 04, 2015 at 05:43:23PM -0400, Anton Aylward wrote:

...

On 06/03/2015 08:34 PM, toothpik wrote:

...
I am running openSUSE v 13.1, konsole v 2.11.3, gvim v 7.4.729

if I start a gvim session from the konsole command line it assumes the same dimensions as konsole -- if I instead start gvim from the alt-F2 run starter it assumes whatever dimensions I have specified in my startup script, or it defaults to a cute 25 line by 80 column display

can someone tell me how to end the tyranny of konsole sizing my gvim windows?

...

I wonder if you have aliasing vis 'search' going on.

no aliases for vim, but I use the heck out of sym-links -- g for gvim and v for vim -- much easier to type and totally irrelevant to the resizing problem

...

if i use 'gvim' i get small windows, but different positions for each of your two use cases.

...

but if in the xterm of the konsole window I run 'vim' or 'vi' it appears as you describe, the complete window.

as it is designed

...

When I run 'alias' I don't see anything to do with vim or gvim or vi Please don't get confused between bash's 'alias' and the email alias mechanism.

yes I know what aliases are in bash -- I have dozens of them for changing directory

...

There is also 'alternatives'. I don't have any set up for vim, gvim or vi

I know what vim I am executing, I compile it myself -- for me it resides on /usr/local/bin, and this too is irrelevant to the resizing problem I have a work-around, alt-F2, and hope we can end this thread -- clearly no-one here knows how to end konsole's tyranny and poking around with irrelevancies is helping no-one -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

I. Petrov

20:29

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, On Fri, 5 Jun 2015, toothpik wrote:

...

On Thu, Jun 04, 2015 at 05:43:23PM -0400, Anton Aylward wrote:

...
On 06/03/2015 08:34 PM, toothpik wrote:

...
I am running openSUSE v 13.1, konsole v 2.11.3, gvim v 7.4.729

if I start a gvim session from the konsole command line it assumes the same dimensions as konsole -- if I instead start gvim from the alt-F2 run starter it assumes whatever dimensions I have specified in my startup script, or it defaults to a cute 25 line by 80 column display

can someone tell me how to end the tyranny of konsole sizing my gvim windows?

...
I wonder if you have aliasing vis 'search' going on.

no aliases for vim, but I use the heck out of sym-links -- g for gvim and v for vim -- much easier to type and totally irrelevant to the resizing problem

...
if i use 'gvim' i get small windows, but different positions for each of your two use cases.

...
but if in the xterm of the konsole window I run 'vim' or 'vi' it appears as you describe, the complete window.

as it is designed

...
When I run 'alias' I don't see anything to do with vim or gvim or vi Please don't get confused between bash's 'alias' and the email alias mechanism.

yes I know what aliases are in bash -- I have dozens of them for changing directory

...
There is also 'alternatives'. I don't have any set up for vim, gvim or vi

I know what vim I am executing, I compile it myself -- for me it resides on /usr/local/bin, and this too is irrelevant to the resizing problem

I have a work-around, alt-F2, and hope we can end this thread -- clearly no-one here knows how to end konsole's tyranny and poking around with irrelevancies is helping no-one

Are you saying that delaying the execution of the .vim file by adding a sleep command at the top of it, does not help ? Did you try to increase the time e.g. to 500ms or 1s ? Regards, I. Petrov -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Signed by Topal iQIcBAEBAgAGBQJVcgaXAAoJEH8sJoKRFRU5rPwP/2SgEsUDjFpdFxJcIqM0bp5y ocGxEJTc7CF8hpCjna+ZpU0l92yDfQRy7d/gVBz5NsjTqdvQT1li9iJOTL2gmirz IM48ADcMEV6ccSN8ywZrxZvTn225m6Bwns53yuo5cKQoSzKrIe38lgfSJXzCVZ/W GFF+pPT1dvRXvfcrSA5RHBxZg/ohIJqZ1c/2VFj3LG9jmlTNmnAausvxxsi74O6/ HxW4o7wdmVJfQPj29gYPqO/sNpWawGz20MgDyLnLqZT0kuTk+106d32vEMH4AS38 3vuFOYodmM8KVNUqbgob4yGIuZQFtjQYNmN9Jv+iy2EDu1Ng/4J7Ne63fNyryuFB Mwd3LyJyvIC30MGtV081S2OCHjY1ckj3a2YUyQL3FNmn1x/ko1KpYnm0XDoFqoM1 Bfyx6rjYbrTRt7iWM3GM49FT+yZd0hudKIaXn75OyoQVV4rsXyaZ2tam99lMqu6/ imY2hq5/yMGbXD5tIqMyGz3jnzxJCeCJ5dqcZI0K7FomIBhfnVUW7s2BH+7Dq8R3 aUdH/Q1xuJH6H52reu50uoetc6dlx4P5hj0YVatajxrv8c+merOohbva9HT4OeUM jv9SIgodYsdFwknIoCTwNSZr0HEtQaqVPTcbnpuD9NPmLAWZlq2E1b7CRveddruP HsAp9ZoNAkK01VPymb3M =DH1w -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

toothpik

21:01

On Fri, Jun 05, 2015 at 11:29:09PM +0300, I. Petrov wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

...

Hello,

...

On Fri, 5 Jun 2015, toothpik wrote:

...

...
On Thu, Jun 04, 2015 at 05:43:23PM -0400, Anton Aylward wrote:

...
On 06/03/2015 08:34 PM, toothpik wrote:

...
I am running openSUSE v 13.1, konsole v 2.11.3, gvim v 7.4.729

if I start a gvim session from the konsole command line it assumes the same dimensions as konsole -- if I instead start gvim from the alt-F2 run starter it assumes whatever dimensions I have specified in my startup script, or it defaults to a cute 25 line by 80 column display

can someone tell me how to end the tyranny of konsole sizing my gvim windows?

...
I wonder if you have aliasing vis 'search' going on.

no aliases for vim, but I use the heck out of sym-links -- g for gvim and v for vim -- much easier to type and totally irrelevant to the resizing problem

...
if i use 'gvim' i get small windows, but different positions for each of your two use cases.

...
but if in the xterm of the konsole window I run 'vim' or 'vi' it appears as you describe, the complete window.

as it is designed

...
When I run 'alias' I don't see anything to do with vim or gvim or vi Please don't get confused between bash's 'alias' and the email alias mechanism.

yes I know what aliases are in bash -- I have dozens of them for changing directory

...
There is also 'alternatives'. I don't have any set up for vim, gvim or vi

I know what vim I am executing, I compile it myself -- for me it resides on /usr/local/bin, and this too is irrelevant to the resizing problem

I have a work-around, alt-F2, and hope we can end this thread -- clearly no-one here knows how to end konsole's tyranny and poking around with irrelevancies is helping no-one

...

Are you saying that delaying the execution of the .vim file by adding a sleep command at the top of it, does not help ? Did you try to increase the time e.g. to 500ms or 1s ?

it "helps," but it isn't a solution: with a second sleep the column setting in the script is honored by the window manager, but the lines setting, while honored by vim, is not honored by the window manager and I wind up with a big swath of lines that aren't really there in the bottom of the window -- there are 42 vim lines and 18 lines of inaccessible nothing -- profoundly weird it does the same with a two second sleep and a five second sleep those inaccessible lines don't go away even after the session has started and I issue a :set lines=42 command -- something in kdm or kde is holding that window to 60 lines and it won't let go unless and until I grab the bottom of the window with the mouse and move it up -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

I. Petrov

22:27

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, It is weird indeed. The windows is resized exatcly as it should for me here. By the way you say that your version of gvim/vim is 7.4.729, but in the official 13.1 reposotiry the latest version is 7.4.052. From where did you installed yours ? Directly from a source (it seems as the latest one according to https://code.google.com/p/vim/source/browse/)? Regards, I. Petrov On Fri, 5 Jun 2015, toothpik wrote:

...

On Fri, Jun 05, 2015 at 11:29:09PM +0300, I. Petrov wrote:

...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

...
Hello,

...
On Fri, 5 Jun 2015, toothpik wrote:

...
...
On Thu, Jun 04, 2015 at 05:43:23PM -0400, Anton Aylward wrote:

...
On 06/03/2015 08:34 PM, toothpik wrote:

...
I am running openSUSE v 13.1, konsole v 2.11.3, gvim v 7.4.729

if I start a gvim session from the konsole command line it assumes the same dimensions as konsole -- if I instead start gvim from the alt-F2 run starter it assumes whatever dimensions I have specified in my startup script, or it defaults to a cute 25 line by 80 column display

can someone tell me how to end the tyranny of konsole sizing my gvim windows?

...
I wonder if you have aliasing vis 'search' going on.

no aliases for vim, but I use the heck out of sym-links -- g for gvim and v for vim -- much easier to type and totally irrelevant to the resizing problem

...
if i use 'gvim' i get small windows, but different positions for each of your two use cases.

...
but if in the xterm of the konsole window I run 'vim' or 'vi' it appears as you describe, the complete window.

as it is designed

...
When I run 'alias' I don't see anything to do with vim or gvim or vi Please don't get confused between bash's 'alias' and the email alias mechanism.

yes I know what aliases are in bash -- I have dozens of them for changing directory

...
There is also 'alternatives'. I don't have any set up for vim, gvim or vi

I know what vim I am executing, I compile it myself -- for me it resides on /usr/local/bin, and this too is irrelevant to the resizing problem

I have a work-around, alt-F2, and hope we can end this thread -- clearly no-one here knows how to end konsole's tyranny and poking around with irrelevancies is helping no-one

...
Are you saying that delaying the execution of the .vim file by adding a sleep command at the top of it, does not help ? Did you try to increase the time e.g. to 500ms or 1s ?

it "helps," but it isn't a solution: with a second sleep the column setting in the script is honored by the window manager, but the lines setting, while honored by vim, is not honored by the window manager and I wind up with a big swath of lines that aren't really there in the bottom of the window -- there are 42 vim lines and 18 lines of inaccessible nothing -- profoundly weird

it does the same with a two second sleep and a five second sleep

those inaccessible lines don't go away even after the session has started and I issue a

:set lines=42

command -- something in kdm or kde is holding that window to 60 lines and it won't let go unless and until I grab the bottom of the window with the mouse and move it up

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Signed by Topal iQIcBAEBAgAGBQJVciJAAAoJEH8sJoKRFRU5gnYP+wcqS5MrNKc5+e2PFdfd3wPO B34tizQEwx19wKWtA93rFhAZhMLYwZ05Ww7tj7iuFHBcO8SZ7fmMaOi/joLMsClJ jficxhYjmaSXw7km3ECNKpB3AAmh6ve1hthPqkBfMwI1i6WkLLj/FOVbv7lBJDFn DpFLh/ELoQR/34h1yIUEa+aMg1hSGQRBzkv0GSF1s+h/B7M4TAv1ruAwVHHCrO6f 3vB4HxhBs0gVxsTq+8ik8H+gXKYvDHC2V2SbcqcPRv9ZXphA0qyviuAzLUJkPiQ3 9eQT8XGN3zeNpJQPEof3RRBXNeGQDnDuthIFrvTGsEPJjiLXAeH1DZC9uOIkCFdA jVZZtAqaUS5yeBKmnYsbxDr6FLzBcJeAUbHYrQKgXoQAY5baSUK8fw1C6P5uOsK0 bqqX3tdVFKwdBYaL3AZ/Bc41Z7A7HusXMpTVg3Go8oFm0Iblx7SlEZWXdQ/U27Jp Y3grCLJjt7o0mgMnf6/HibGNgUNncSYP1p2VrMPvc0WSvmNQBUh9dJDsDVIW5CuC NXkVXebJpMIgDU0j1E9WQ8INJzgWkY3p3JEh8eWAfK8UDQq4FYJ3vwGDz0Fr1gba VW6pYmDNBK8DSyskC3VMT2d0+Z6JLhYTXayeoWjNuCqnMDAGJY3IK2EDhNsXBgfW kDOzebZE1nwaqPyl2qDS =juQa -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

toothpik

22:51

On Sat, Jun 06, 2015 at 01:27:10AM +0300, I. Petrov wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

...

Hello,

...

It is weird indeed. The windows is resized exatcly as it should for me here. By the way you say that your version of gvim/vim is 7.4.729, but in the official 13.1 reposotiry the latest version is 7.4.052. From where did you installed yours ? Directly from a source (it seems as the latest one according to https://code.google.com/p/vim/source/browse/)?

yes I roll my own -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Anton Aylward

6 Jun 6 Jun

02:11

On 06/05/2015 05:01 PM, toothpik wrote:

...

I wind up with a big swath of lines that aren't really there in the bottom of the window -- there are 42 vim lines and 18 lines of inaccessible nothing -- profoundly weird

I'm not sure what you are describing there but one way I can interpret this is normal behaviour. If I have a 10 line program and display it in a 20 -- or 42 -- line window what is going to appear on the bottom 10 -- or 32 -- lines in the window? Those bottom lines are 'inaccessible' in that I can move the cursor up and down the 10 lines of the program but not into the remaining area. This makes perfect sense to me. If this is not what you are describing, please try to describe it better. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

toothpik

09:08

On Fri, Jun 05, 2015 at 10:11:46PM -0400, Anton Aylward wrote:

...

On 06/05/2015 05:01 PM, toothpik wrote:

...
I wind up with a big swath of lines that aren't really there in the bottom of the window -- there are 42 vim lines and 18 lines of inaccessible nothing -- profoundly weird

...

I'm not sure what you are describing there but one way I can interpret this is normal behaviour.

...

If I have a 10 line program and display it in a 20 -- or 42 -- line window what is going to appear on the bottom 10 -- or 32 -- lines in the window?

...

Those bottom lines are 'inaccessible' in that I can move the cursor up and down the 10 lines of the program but not into the remaining area.

...

This makes perfect sense to me.

...

If this is not what you are describing, please try to describe it better.

no -- too much trouble when it's plain you're not going to be able to help -- please Anton, I appreciate your efforts but they are wasted here -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

3248

Age (days ago)

3251

Last active (days ago)

List overview

Download

27 comments

7 participants

participants (7)

Andrei Borzenkov
Anton Aylward
David Haller
I. Petrov
Linda Walsh
Patrick Shanahan
toothpik