Re: [Lynx-dev] Still some display problems (dev.13)

2005-10-19 Thread Thorsten Glaser
Thomas Dickey dixit:

Though a quick check adding a br or p after the /pre doesn't help.
Removing the blanks does.  This isn't a new problem.  Comparing with IE,
I see that it puts out the blanks, but puts a carriage return after them.
Opera is doing the same thing.

I don't necessarily think forcing a line feed and carriage return after a
/pre is a good thing to do, but as long as it fixes this issue...

Thanks!

bye,
//mirabile
-- 
I believe no one can invent an algorithm. One just happens to hit upon it
when God enlightens him. Or only God invents algorithms, we merely copy them.
If you don't believe in God, just consider God as Nature if you won't deny
existence.  -- Coywolf Qi Hunt


___
Lynx-dev mailing list
Lynx-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/lynx-dev


Re: [Lynx-dev] Still some display problems (dev.13)

2005-10-19 Thread Thomas Dickey

On Wed, 19 Oct 2005, Thorsten Glaser wrote:


Thomas Dickey dixit:


Though a quick check adding a br or p after the /pre doesn't help.
Removing the blanks does.  This isn't a new problem.  Comparing with IE,
I see that it puts out the blanks, but puts a carriage return after them.
Opera is doing the same thing.


I don't necessarily think forcing a line feed and carriage return after a
/pre is a good thing to do, but as long as it fixes this issue...


It did seem an ugly solution, but I guess the gcc people tuned it against
mozilla, which in turn means it works just like IE

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net


___
Lynx-dev mailing list
Lynx-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/lynx-dev


[Lynx-dev] Still some display problems (dev.13)

2005-08-24 Thread Thorsten Glaser
http://gcc.gnu.org/gcc-4.1/changes.html

Terminal: XFree86(R) 4.5.0 xterm at 113x42; GNU screen with permanent
status bar inside (leaving 113x41 for lynx).

[...]
  if (d)
 
{   
 
  foo (b, c); 
 
  a = b + c;
 
}   
 
  printf (%d\n, a);   
 
}   
 
   The  a  =  b  +  c  can  be  sunk  to right before the printf. 
Normal code sinking will not do thi
   it  will  sink  the  first one above into the else-branch of the 
conditional jump, which still gives  
   you two copies of the code.  
 
[...]

I see this quite often, some things are just outside the screen;
for example, if I had not had links and form fields are numbered
I'd not seen the login button of a page once...

//mirabile
-- 
I believe no one can invent an algorithm. One just happens to hit upon it
when God enlightens him. Or only God invents algorithms, we merely copy them.
If you don't believe in God, just consider God as Nature if you won't deny
existence.  -- Coywolf Qi Hunt


___
Lynx-dev mailing list
Lynx-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/lynx-dev


Re: [Lynx-dev] Still some display problems (dev.13)

2005-08-24 Thread Thomas Dickey
On Wed, Aug 24, 2005 at 09:45:16AM +, Thorsten Glaser wrote:
 http://gcc.gnu.org/gcc-4.1/changes.html
 
 Terminal: XFree86(R) 4.5.0 xterm at 113x42; GNU screen with permanent
 status bar inside (leaving 113x41 for lynx).
 
 [...]
   if (d)  

 { 

   foo (b, c);   

   a = b + c;  

 } 

   printf (%d\n, a); 

 } 

The  a  =  b  +  c  can  be  sunk  to right before the printf. 
 Normal code sinking will not do thi
^^^
The extra blanks are from the pre section above, e.g.,

  if (d)
{
  foo (amp;b, amp;c);
  a = b + c;
}
  printf (%d\n, a);
}
/pre

The codea = b + c/code can be sunk to right before the
codeprintf/code.  Normal code sinking will not do this, it will
sink the first one above into the else-branch of the conditional

Though a quick check adding a br or p after the /pre doesn't help.
Removing the blanks does.  This isn't a new problem.  Comparing with IE,
I see that it puts out the blanks, but puts a carriage return after them.
Opera is doing the same thing.

it  will  sink  the  first one above into the else-branch of the 
 conditional jump, which still gives  
you two copies of the code.

 [...]
 
 I see this quite often, some things are just outside the screen;
 for example, if I had not had links and form fields are numbered
 I'd not seen the login button of a page once...
 
 //mirabile
 -- 
 I believe no one can invent an algorithm. One just happens to hit upon it
 when God enlightens him. Or only God invents algorithms, we merely copy them.
 If you don't believe in God, just consider God as Nature if you won't deny
 existence.-- Coywolf Qi Hunt
 
 
 ___
 Lynx-dev mailing list
 Lynx-dev@nongnu.org
 http://lists.nongnu.org/mailman/listinfo/lynx-dev

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net


___
Lynx-dev mailing list
Lynx-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/lynx-dev