Issue 726: overly wide progress message fills screen... - Darcs bug tracker

Title	overly wide progress message fills screen...
Priority	feature	Status	resolved
Superseder		Nosy List	SamB, beschmi, droundy, kowey, tommy
Assigned To		Topics

Created on 2008-03-05.03:54:15 by SamB, last changed 2008-03-28.18:44:03 by droundy.

msg3751 (view)	Author: SamB	Date: 2008-03-05.03:54:14
Messages			(mbox)
For instance: Reading patches from /home/naesten/hacking/haskell/ghc-hashedrepo/libraries/byte Reading patches from /home/naesten/hacking/haskell/ghc-hashedrepo/libraries/byte Reading patches from /home/naesten/hacking/haskell/ghc-hashedrepo/libraries/byte Reading patches from /home/naesten/hacking/haskell/ghc-hashedrepo/libraries/byte Reading patches from /home/naesten/hacking/haskell/ghc-hashedrepo/libraries/byte Reading patches from /home/naesten/hacking/haskell/ghc-hashedrepo/libraries/byte Reading patches from /home/naesten/hacking/haskell/ghc-hashedrepo/libraries/byte Reading patches from /home/naesten/hacking/haskell/ghc-hashedrepo/libraries/byte Reading patches from /home/naesten/hacking/haskell/ghc-hashedrepo/libraries/byte Reading patches from /home/naesten/hacking/haskell/ghc-hashedrepo/libraries/byte
msg3765 (view)	Author: droundy	Date: 2008-03-05.15:23:03
Is the problem that the message is wider than your screen? The message is 80 chars wide, which is the de facto standard for screen width. What do you recommend instead? Do you think the only adequate solution is to use a library such as libcurses to find out the actual terminal width? David
msg3767 (view)	Author: SamB	Date: 2008-03-05.16:43:58
On Wed, Mar 5, 2008 at 10:23 AM, David Roundy <bugs@darcs.net> wrote: > Is the problem that the message is wider than your screen? The message is 80 > chars wide, which is the de facto standard for screen width. What do you > recommend instead? Do you think the only adequate solution is to use a library > such as libcurses to find out the actual terminal width? Actually, there was more to the messages (that was actually the bytestring repository), which got wrapped onto the next line. Then, when it was time to display the next message, darcs cleared that line only and displayed another one. I wasn't very coherent last night, was I?
msg4072 (view)	Author: droundy	Date: 2008-03-28.18:44:02
I think this is fixed...

Browse related patches: unstable | stable

History
Date	User	Action	Args
2008-03-05 03:54:16	SamB	create
2008-03-05 15:23:04	droundy	set	priority: bug -> feature nosy: droundy, tommy, beschmi, kowey, SamB status: unread -> chatting messages: + msg3765
2008-03-05 15:23:29	droundy	set	nosy: droundy, tommy, beschmi, kowey, SamB title: overly wide progress message fills screen... -> overly wide progress message fills screen with width < 80 chars...
2008-03-05 16:43:59	SamB	set	nosy: droundy, tommy, beschmi, kowey, SamB messages: + msg3767 title: overly wide progress message fills screen with width < 80 chars... -> overly wide progress message fills screen...
2008-03-28 18:44:03	droundy	set	status: chatting -> resolved nosy: droundy, tommy, beschmi, kowey, SamB messages: + msg4072