Age | Commit message (Collapse) | Author |
|
Ignore-this: 32164dfb4309af09754d8a6ed0749f0d
It's basically an alias for `paredit-in-string-escape-p' now.
Replacing one by the other would make too big a diff.
darcs-hash:20110411230056-00fcc-d2838af6bff48ed698f596abfc345453f1bfad63
|
|
Ignore-this: 186d2611fcbd98479c898a8b756d01ee
darcs-hash:20110411225827-00fcc-27d7a8defd057cb7640fa223e20e110e34f85db8
|
|
Ignore-this: ce30323a4077d83acc1967af18604e40
Put the new escape after the one the point is on; don't split it.
darcs-hash:20110411225316-00fcc-1c65c221a9878047104d5fed02a60f48f0641f7b
|
|
Ignore-this: ed55179d0138b72dbe408836bb9f9403
It should move past the close, not stay where it is.
`paredit-move-past-close-and-newline' already did this; the two now
share the common code.
darcs-hash:20110411225030-00fcc-202b9f3f93aab76ddae1c8bb10f9f605fee949d4
|
|
Ignore-this: ea283af1a5a27d8d3fe32647e8aa5910
darcs-hash:20110411190348-00fcc-7a8d049f8be17ea0ffec1070fe7ae7a58d0f47be
|
|
Ignore-this: 51d8b01dc3a61efe5b0e0c651bf3a812
New command `paredit-delete-region' is to `delete-region' as
`paredit-kill-region' is to `kill-region'.
Deleting a region that starts or ends in a comment works a little
better now.
`paredit-kill-ring-save' is no more: paredit doesn't (and shouldn't)
keep you from putting unbalanced text into the kill ring. What it
should (but doesn't yet) do is keep you from yanking unbalanced text
into the buffer.
darcs-hash:20110411184530-00fcc-e20733f7a36482041cb9279030d66a9419fa4e9b
|
|
Ignore-this: 15f19e277834ce01b503d4adde69f56e
darcs-hash:20110411180857-00fcc-c3b0a9464be06835aaf1ce7fb06034c31705ea37
|
|
Ignore-this: db6c2b72e92eadc7b98d3c0613916f9d
darcs-hash:20110411180500-00fcc-5e23c6d9675a260d692830ecdc40302d4ab52141
|
|
Ignore-this: c75566b3db4425b39ca633d55c6d400e
In `paredit-check-region', call `paredit-region-ok-p' to discern
whether the region is OK before narrowing and calling `check-parens'
to report any errors. This avoids unwanted point motion if the
region is OK, or if it isn't, lets `check-parens' move the point to
the part where the region is not OK.
Write docstrings for the two routines.
darcs-hash:20110411180300-00fcc-674d77c0c9566bcfb8ef7cfe88a50de34a373853
|
|
Ignore-this: 3f246298c4207e54bdecd05647c0c8fd
darcs-hash:20110410005917-00fcc-7fbd486327b26986ca2b30698a4c1e07b1b1b326
|
|
Ignore-this: 18f0bece3d6a499eaec1befe180a4faf
darcs-hash:20110409200610-00fcc-05f1a5029eaea4ab0600bb5ee3dfeb5efff55761
|
|
Ignore-this: eb090de24ae6a8502605aefee51420a4
Emacs may have indentation methods that rely on the buffer's being
balanced.
The change to `paredit-forward-barf-sexp' is OK because when
`paredit-forward-and-indent' calls `indent-region', the point will be
on the same line as the closing delimiter, so it will get indented
correctly.
Add regression tests.
darcs-hash:20110409182523-00fcc-5ed49a704f12afa1fb9353eb8dcd5d97e963964c
|
|
Ignore-this: 4f33f1efd97dfb7cc0041be7f4d5ccee
darcs-hash:20110323154254-00fcc-4498047b5a31bbe15f51727605972723005babd4
|
|
Ignore-this: 8fa112b5321c5367a246d1bfd1499485
Of course, I haven't tested this in a long time, but that's the first
version released after paredit 20, which was the first version of
paredit to include XEmacs compatibility hacks.
darcs-hash:20110323154050-00fcc-ea1ef7a12f17db3dd7e4702071ad50df438489e5
|
|
Ignore-this: 48046ba29e4172c407b0d44fbbe4a7a0
darcs-hash:20110323062311-00fcc-820fab4a894bf7175f200900ff32d2daf7569620
|
|
Ignore-this: 6d25fd1fad7e584d421b9e57fa8ab69
At least one user, upon seeing Emacs say `Escaping character...',
checked top for its CPU usage!
Thanks, elly.
darcs-hash:20110323061213-00fcc-63e99f496e8afd219d3c5ea88f6499abcd4ade39
|
|
Ignore-this: 3a37e719407c3fbd2e3cfe9256d7598a
darcs-hash:20110323045451-00fcc-dd611d727eb018f1ce6ab8ba4560bce2313ea54d
|
|
Ignore-this: 18cf22cb9511351b0d547a2337357c96
There is no semantic difference here in elisp, since elisp guarantees
left-to-right evaluation order in `let', but using `let*' makes it
clearer that there is an intended ordering dependency.
darcs-hash:20110323043646-00fcc-fddfd7cf6d1d67eea90fa03627a510d7c82432b4
|
|
Ignore-this: a404afd4e847db4ef89b17de42d431e4
It was copied & pasted from `paredit-forward-delete-in-comment'
incautiously and lacked a necessary `save-excursion'.
darcs-hash:20110323034916-00fcc-55ea95fc6be8f4b57fbadfd2c8cc04942dbd2b1e
|
|
Ignore-this: 617dee9b848d79adfb69c7c8ad53e3f6
New command `paredit-recenter-on-defun'.
Thanks to Eitan Postavsky for the report.
darcs-hash:20110323002413-00fcc-1b422d9a7c39f930a862f8917cec8a868fa066b0
|
|
Ignore-this: 1f0109619737b5836077f22e651dc390
Avoids dangling opening delimiters in `paredit-insert-pair'.
darcs-hash:20110322221620-00fcc-dff68effdbbb1b95f5b6d5c142e1ba4bb48bf3e5
|
|
Ignore-this: 13da51d89ea973b30048035bea3ac499
This way, M-3 ( works mostly like M-3 M-(. (They still behave
differently with respect to `paredit-yank-pop', though.)
darcs-hash:20110322204957-00fcc-3cbe3616018abf120000169ad818b1d86de9bdcb
|
|
Ignore-this: efc4abdd6f8e015ae35c51dea4358a1e
darcs-hash:20110322203605-00fcc-a82f3ae4e936b16d682cbb26279dfa1d59c4dd33
|
|
Ignore-this: 386250d19d31621eb42085a40d09f3c7
darcs-hash:20110322202808-00fcc-4dafc1661f29279fed56e15ddafbb4268776a654
|
|
Ignore-this: b888afcbabc7b807c27c4ce43dd19d39
darcs-hash:20110322202749-00fcc-d8db79b9f923d263f06e4da2a933751f3d7ecef2
|
|
Ignore-this: 413110413c3753fa63a9cb9495bf6e95
darcs-hash:20110322202747-00fcc-4de3ea37975f7dc92079b290e1fe37f53fe2e4f8
|
|
Ignore-this: c5c86de0f646ccce29ee055a85a8ddd0
darcs-hash:20110322202602-00fcc-1629f9e79df478d86ca8206e5cb95ad13de8f2e5
|
|
Ignore-this: 710cb2e344eaf6c42c0964dd5481afd6
This way, C-d with
;foo|
(bar
baz)
won't result in an unbalanced buffer: paredit will instead scream at
you.
darcs-hash:20110322202415-00fcc-5291a11ee2e8ffba82602c519957fcc482165d30
|
|
Ignore-this: 5c42517877a1692148a110e6abd8f46f
darcs-hash:20110322185212-00fcc-6d95cd1cdfce465d61e17dd80217d81e53d6e2cd
|
|
Ignore-this: 8b61d4754546201aba818d696cad6dcf
darcs-hash:20110322075600-00fcc-0ceb112f64613ab534c2f6a5e33dea13eb8825e6
|
|
Ignore-this: ad4e061915d387d246846932d5860919
darcs-hash:20110322075338-00fcc-ac9a1c13fd14ea9dd9b5070b66cdd3549cadc25a
|
|
Ignore-this: 799e1e911ebd252aec4ce53d85935236
Don't break the line if the point is at the end of the line already,
or if the point is on the last line of the buffer and there is no
trailing line break.
darcs-hash:20110322074906-00fcc-768c7e264b5142c25909573edaf157b79a44ccbb
|
|
Ignore-this: d2194315bd70974f87169d0dfd7be139
darcs-hash:20110322074841-00fcc-debcbca68041c58ba94327de6a3594f6e924e8d6
|
|
Ignore-this: 9882470551c262e697c684cef48b64e2
darcs-hash:20110322074814-00fcc-8d7391b78a3aa4650142dfa57bd7353fd670989a
|
|
Ignore-this: 345bd5a93c031a016fa07d242baa18f2
darcs-hash:20110322074730-00fcc-25059d738514de98e1ba3e3c0e8f08ad3f207e6a
|
|
Ignore-this: 168f652fb4acfc783a92c0f7af2404eb
As it was written, `paredit-comment-dwim' would choose a top-level
comment instead. Wrapping the two forms in (zot ...) makes it
clearer what's going on anyway.
darcs-hash:20110322074609-00fcc-a04368f7f7905ff131ccbf70a6a761a89178dcc8
|
|
Ignore-this: be5f049e889ab7a076cdf4a2eab7369
darcs-hash:20110322074546-00fcc-6744cf575d75ead5a11dd49779f8b17c7aac1819
|
|
Ignore-this: b621fcd8a09c31b699991b81e5526147
darcs-hash:20110322074502-00fcc-79dfb5b734ed93fcb7bad736f6a94fbd79d130b4
|
|
Ignore-this: c058945ef1f3c5590c36a034121811e8
Insert whitespace if it may be necessary.
Thanks to Eitan Postavsky for the bug report.
darcs-hash:20110322074446-00fcc-e3303edd5c9055a9687d22f99379d23f8879eba7
|
|
Ignore-this: 1b8fe110a0983c730918eb16ed81911a
Suggested by Eitan Postavsky.
I'm not yet sure this is right (and I'm not yet sure of the similar
change to `paredit-count-sexps-forward' and thus `C-u M-('), but I'll
try it out.
darcs-hash:20110320194242-00fcc-635c1cdba60f9a6b395561a64349876b6e524d29
|
|
Ignore-this: 5116ca507a480c4bb4cfe95b9ab34820
This enables the use of the safer `paredit-handle-sexp-errors'
instead of `condition-case' for these purposes.
darcs-hash:20110320192038-00fcc-e4799c56417a15787ca03f8b06962718412bbe88
|
|
Ignore-this: 8ca077b074853d64639e83f4a81dcd73
darcs-hash:20110320190601-00fcc-54e85aa35638a194de67b28be83fcf65575d7adf
|
|
Ignore-this: 5d7b87a61c56931aa9df39a6c6c7df58
No more GNU Emacs 20.
darcs-hash:20110320185519-00fcc-251fd8bafde8103581af11f59f331ad940b29e81
|
|
Ignore-this: 8fa60f5bd8c398aa31f91b26c4affb12
Set to `paredit-override-check-parens-interactively' if you want to
be prompted whether to enable Paredit Mode rather than to have `M-x
paredit-mode RET' simply barf if there are unbalanced parentheses.
(Someone suggested this to me months ago, but I have forgotten who.)
Assume we have `check-parens'. No more GNU Emacs 20.
darcs-hash:20110320185342-00fcc-30abf28738cf76cca1d16f02b2f26f3f46525c44
|
|
Ignore-this: 76e5c8178ddc5dede762dc101e526095
Use the atrocious idiom (while (setq tmp ...) ...)...
darcs-hash:20110320184537-00fcc-ad46fdaac5b45670aa781cd61c105e1ee6ade7f5
|
|
Ignore-this: 710e264ca330414cfb55c295d0ed5f46
Fixes `C-u M-(' at the top level when there is whitespace at the end
of the buffer: the closing delimiter should go at the end of the last
S-expression, not at the end of the buffer after the whitespace.
Thanks to Eitan Postavsky for the report.
darcs-hash:20110320183854-00fcc-7162d40b9111aed39ca72a913393af8bb2425025
|
|
Ignore-this: 9c3342808317128eefc0b83bf63cfb15
Also use `lisp-fill-paragraph' rather than `fill-paragraph'.
Thanks to Eitan Postavsky for the suggestion.
darcs-hash:20110320183704-00fcc-d64d8a2d2e06db8a206a0fadb3b9dbe0f8c10abf
|
|
Ignore-this: 4bf62fadcc0f90e2c582311eff1355d8
Check for the beginning/end of buffer to avoid infinite loops there.
Order points right to fix (|"foo" ()) ==C-M-d==> ("foo" (|)).
Thanks to Eitan Postavsky for the report.
darcs-hash:20110320183422-00fcc-8fe38d45bdd4e4e94925d56f537fd079111514f6
|
|
Ignore-this: 316cb4a43f14464fbcc655c61926f177
Thanks to Eitan Postavsky for the suggestion.
darcs-hash:20110320174113-00fcc-bc6d366e415e031be7bb6faa7353caabcd3d9c57
|
|
Ignore-this: 13c949425c6b6df35b26e53d9e1819e6
Comment referenced no longer extant text in the file, and credits are
moving to another file.
darcs-hash:20110320173549-00fcc-4c0751e61f57f437bb8b0b9f6c8d861f20757023
|