On Sun, Nov 13, 2022 at 07:16:43PM -0500, Thomas Dickey wrote: > On Sun, Nov 13, 2022 at 09:55:18PM +0000, Chris Green wrote: > > On Sun, Nov 13, 2022 at 03:40:43PM -0500, Thomas Dickey wrote: > > > On Sun, Nov 13, 2022 at 08:11:17PM +0000, Chris Green wrote: > > > > On Sun, Nov 13, 2022 at 10:55:07AM -0500, Thomas Dickey wrote: > > > > > On Sun, Nov 13, 2022 at 01:57:30PM +0000, Chris Green wrote: > > > > > > This relates to my recent posting about trying to use the '-c' > > > > > > command > > > > > > line option. However it's now a more general problem/question. > > > > > > > > > > > > Whenever I add a '-c command' (or a '+ command', or a '-g NNN') to > > > > > > the > > > > > > command line vile opens two windows, the file I want is in the first > > > > > > window and the following is in the second (lower) window:- > > > > > > > > > > > > [Reading /home/chris/.vilerc] > > > > > > > > > > perhaps your .vilerc doesn't set nopopup-msgs (or sets popup-msgs) > > > > > > > > > My .vilerc is:- > > > > > > > > > > > ... > > > > source digraphs.rc > > > > > > > > But it's happenning before reading .vilerc isn't it? > > > > > > no - it's happening because of the warning message: > > > > > > * If no warning messages were encountered during startup, and the > > > popup-msgs > > > * mode wasn't enabled, discard the informational messages that are there > > > * already. > > > > > > you could do this > > > > > > vile -c goto-end-of-file > > > > > Ah! Thank you, that does what I need. > > > > However I'm still a little confused, when you say "it's happening > > because of the warning message", am I getting a warning message? If > > so, what is it? ... and can I stop it? > > The error message was this - > > "/home/chris/wiki/data/pages/boating/diary/2011/05/20.txt"] > > [Not that many lines in buffer: 20]
Oh, I see. I don't think the error was causing the second window to open though. I think my problem was confusion (mine) about what commands one can put after the '-c'. The commands have to be ones that work at the : prompt and I wasn't realising that. What I was doing was entering single letter commands which, if entered at the : simply wait for more input. Thanks for your help. -- Chris Green