Mercurial > hg > xemacs-beta

comparison src/text.c @ 5384:3889ef128488

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Fix misspelled words, and some grammar, across the entire source tree. See xemacs-patches message with ID <AANLkTi=edkEKtK3pZ60ytsG5pTJQy2TjAEVCZCLOa-oA@mail.gmail.com>.
author Jerry James <james@xemacs.org>
date Thu, 24 Mar 2011 11:00:11 -0600
parents 71ee43b8a74d
children 4dee0387b9de
comparison
equal deleted inserted replaced
5383:294ab9180fad 5384:3889ef128488
548 548
549 April 11, 2000 549 April 11, 2000
550 550
551 Well yes, this was the whole point of my "no lossage" proposal of being 551 Well yes, this was the whole point of my "no lossage" proposal of being
552 able to undo any coding-system transformation on a buffer. The idea was 552 able to undo any coding-system transformation on a buffer. The idea was
553 to figure out which transformations were definitely reversable, and for 553 to figure out which transformations were definitely reversible, and for
554 all the others, cache the original text in a text property. This way, you 554 all the others, cache the original text in a text property. This way, you
555 could probably still do a fairly good job at constructing a good reversal 555 could probably still do a fairly good job at constructing a good reversal
556 even after you've gone into the text and added, deleted, and rearranged 556 even after you've gone into the text and added, deleted, and rearranged
557 some things. 557 some things.
558 558
587 -------------------------------------------------------------------------- 587 --------------------------------------------------------------------------
588 April 11, 2000 588 April 11, 2000
589 589
590 Well yes, this was the whole point of my "no lossage" proposal of being 590 Well yes, this was the whole point of my "no lossage" proposal of being
591 able to undo any coding-system transformation on a buffer. The idea was 591 able to undo any coding-system transformation on a buffer. The idea was
592 to figure out which transformations were definitely reversable, and for 592 to figure out which transformations were definitely reversible, and for
593 all the others, cache the original text in a text property. This way, you 593 all the others, cache the original text in a text property. This way, you
594 could probably still do a fairly good job at constructing a good reversal 594 could probably still do a fairly good job at constructing a good reversal
595 even after you've gone into the text and added, deleted, and rearranged 595 even after you've gone into the text and added, deleted, and rearranged
596 some things. 596 some things.
597 597