On Sat, Nov 30, 2019 at 03:44:49PM -0500, Marco Sirabella <ma...@sirabella.org>
wrote:
> My question: What's a better way to do this? Initially working with
> `saveLines`, I tried `*Rxvt.saveLines: 0` & `*Rxvt.saveLines: -1` to see if
> there were any options for "infinite scrollback", but those unfortunately
> didn't work.
As a sidenote, saveLines 0 does work, giving you zero savelines.
> It doesn't look like rxvt is dynamically allocating for the scrollback buffer
> either, just allocating the max.
urxvt does dynamically allocate memory on anything resembling a modern
system - for example, 1000000 saveLines alocate about 15MB on my current
GNU/Linux system initially, and it grows from there. urxvt reserves
address space, it doesn't actually allocate the memory (virtual memory is
not real memory).
> Is there functionality for dynamically infinite scrollback buffer?
That seems very dangerous - a simple mistyped command (e.g. "yes") could
crash a system in a split second if it were unbounded. It also seems to
have no or very little benefit?
> Is there interest? Would you accept a contribution towards that?
What would the use case be? The use case would need to be very convincing
as to motivate a likely very high increase in complexity.
Note that there are long term plans to compress the history in some
way, as history can become very large. This would certainly be the more
important use case, and shouldn't be hindered by any changes to the line
management.
Greetings,
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / schm...@schmorp.de
-=====/_/_//_/\_,_/ /_/\_\
_______________________________________________
rxvt-unicode mailing list
rxvt-unicode@lists.schmorp.de
http://lists.schmorp.de/mailman/listinfo/rxvt-unicode
