[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#921191: RFP: edit-indirect -- Edit regions in separate buffers, like `org-edit-src-code' but for arbitrary regions



Package: wnpp
Severity: wishlist

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

* Package name    : edit-indirect
  Version         : 0.1.5
  Upstream Author : Fanael Linithien <fanael4@gmail.com>
* URL             : https://github.com/Fanael/edit-indirect.git
* License         : BSD
  Programming Lang: emacs-lisp
  Description     : Edit regions in separate buffers, like `org-edit-src-code' but for arbitrary regions

Edit the region BEG..END in a separate buffer.
The region is copied, without text properties, to a separate
buffer, called edit-indirect buffer, and
`edit-indirect-guess-mode-function' is called to set the major
mode.
When done, exit with `edit-indirect-commit', which will remove the
original region and replace it with the edited version; or with
`edit-indirect-abort', which will drop the modifications.

This differs from `clone-indirect-buffer' with narrowing in that
the text properties are not shared, so the parent buffer major mode
and the edit-indirect buffer major mode will not be able to tread
on each other's toes by setting up potentially conflicting text
properties, which happens surprisingly often when the font-lock
mode is used.

This should be maintained by the emacs-addons-team. If no-one else is
inspired, I'll eventually get around to packaging it.

There is preliminary packaging at

      https://salsa.debian.org/emacsen-team/edit-indirect

-----BEGIN PGP SIGNATURE-----

iQGzBAEBCAAdFiEE3VS2dnyDRXKVCQCp8gKXHaSnniwFAlxWCGIACgkQ8gKXHaSn
nizAsAv6AlH8FrLzm8DQVxJWQwh25fhJKIpMqCZm41+UyVhWvtUBVLRL2lunVeuJ
3I48bcDr8z764uSgpAsnh58dXWiid9HLIUgKMg6NpO5tMlKUqkdQK7zrQrhkQZ3w
fHAQdgBi6vQVHoeXyD3hGcoiAT7oXtzQkVMLs+8DCz06+W/XLUmCl8y0zRB4r+Rl
gB3ZtidE4mznNKagqNy9FGh7iDI7LRqIky0/ap7jvvTz8y8OYStRITPQpcxxLJsl
j9DLERDkTEubtyz0XEOSr+Ql1j67YkeMIwNzxm5RzzxwCspDVz/SRJ0yNTQ/sEm7
3/QtbDsTWpPPngEHDM8i0F6WMyJH4YSOO6uCabhdk20ERdH4Aa9a8pN9+XvJ84dD
r+iVcvUzMFtXxWOPtgHxOLOk6HdgDmKUpXsmfgY7KGpC1NymJ+bDPT5eVpd84L62
1Po1fEdW3d7s4U8bhz3Tqf5ewWF+et+qyd+XFLW5DjFksIwYGmHUPr9LkEa6ROHk
OrDVXT+j
=MrLQ
-----END PGP SIGNATURE-----


Reply to: