Matthieu Moy <[EMAIL PROTECTED]> writes: > Before going for an incremental parser, did you try profiling the > existing code? I don't know exactly which part is problematic > performance-wise, and if the code can be made fast enough, it doesn't > need to be incremental.
I haven't tried that yet, but I will before starting on this.
> Another idea I had was to run
>
> git log | some-script-that-transform-it-into-lisp
>
> and to just `load-file' the result. If Emacs can't parse the log fast
> enough, perhaps another script can.
No. (1) Not incremental. (2) Introduces an unnecessary external
dependency, which are generally a pain to work with.
> As for your idea, perhaps `set-process-filter' could help, too.
When doing that, I think it may still be possible to catch log output
mid-line or mid-stanza. To solve that, I would have to insert output
accumulatively into a buffer anyway. So a filter function would be
completely unnecessary.
--
Michael Olson -- FSF Associate Member #652 |
http://mwolson.org/ -- Jabber: mwolson_at_hcoop.net | /` |\ | | |
Sysadmin -- Hobbies: Lisp, GP2X, HCoop | |_] | \| |_|
Projects: Emacs, Muse, ERC, EMMS, ErBot, DVC, Planner |
pgpK9T7Rsxzbk.pgp
Description: PGP signature
_______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
