Hi,
I'm using quite often the wonderful Clipboard History functionality but …
since I see the improvements to be able to work with larger text files, I'm also copying larger text chunks (from 1MB to 5MB) across documents and applications resp. If I do this the Clipboard History (in conjunction with TM) becomes unresponsive and I've to kill TM. I also can't delete the Clipboard History due to the fact that I've to open window in beforehand. The only chance is to delete the Clipboard History physical files.
I wonder if one could improve it a bit. Here some thoughts:
- make it possible to delete the Clipboard History from outside that window (maybe in conjunction with the chance to delete only those entries which are large than xy kBytes)
- make it possible to terminate the opening of the window if the size is too large
To avoid such unresponsive behaviour in generell
- one also could think of to restrict the size of an entry which should be stored, i.e. let's say store only the clipboard content if the size is less than xy kBytes [I think this is the easiest way]
- or if the Clipboard History is called load into the TableView only "a preview or head" (only the first 10 kBytes or so - and which can be hold in a different DB) of the stored items and if the user starts searching the search will be performed outside of the TableView (in file/database)
Is not an urgent issue but … ;)
Kind regards, Hans
On 26 Mar 2014, at 17:07, Hans-Jörg Bibiko wrote:
- or if the Clipboard History is called load into the TableView only
"a preview or head" (only the first 10 kBytes or so
Next build will limit it to around 1024 “code points”: https://github.com/textmate/textmate/commit/2cc71e57f9852905764a496e488a10ac...
- and which can be hold in a different DB) of the stored items and if
the user starts searching the search will be performed outside of the TableView (in file/database)
Hopefully the above should fix it, but let me know if you see a performacne issue (after next build) as it still does load the entire entry¹ (when bringing up the history viewer), which could be split up into the full column and a summary (as you suggest).
¹ It’s using CoreData so I _think_ entries are loaded “as they are shown”, meaning only the items visible are initially loaded, not the entire database.
Many thanks for the quick answer and fix resp. :)
I'll try and let you know if I find an issue.
Cheers, Hans
On 26 Mar 2014, at 11:49, Allan Odgaard mailinglist@textmate.org wrote:
On 26 Mar 2014, at 17:07, Hans-Jörg Bibiko wrote:
- or if the Clipboard History is called load into the TableView only "a preview or head" (only the first 10 kBytes or so
Next build will limit it to around 1024 “code points”: https://github.com/textmate/textmate/commit/2cc71e57f9852905764a496e488a10ac...
- and which can be hold in a different DB) of the stored items and if the user starts searching the search will be performed outside of the TableView (in file/database)
Hopefully the above should fix it, but let me know if you see a performacne issue (after next build) as it still does load the entire entry¹ (when bringing up the history viewer), which could be split up into the full column and a summary (as you suggest).
On 26 Mar 2014, at 12:01, Hans-Jörg Bibiko bibiko@eva.mpg.de wrote:
I'll try and let you know if I find an issue.
Hi Allan,
I've just compiled the latest TM version and so far it works like charm. Thanks for the fix!
Cheers, Hans
-
Allan Odgaard -
Hans-Jörg Bibiko