ÿØÿàJFIFÿþ ÿÛC       ÿÛC ÿÀÿÄÿÄ"#QrÿÄÿÄ&1!A"2qQaáÿÚ ?Øy,æ/3JæݹÈ߲؋5êXw²±ÉyˆR”¾I0ó2—PI¾IÌÚiMö¯–þrìN&"KgX:Šíµ•nTJnLK„…@!‰-ý ùúmë;ºgµŒ&ó±hw’¯Õ@”Ü— 9ñ-ë.²1<yà‚¹ïQÐU„ہ?.’¦èûbß±©Ö«Âw*VŒ) `$‰bØԟ’ëXÖ-ËTÜíGÚ3ð«g Ÿ§¯—Jx„–’U/ÂÅv_s(Hÿ@TñJÑãõçn­‚!ÈgfbÓc­:él[ðQe 9ÀPLbÃãCµm[5¿ç'ªjglå‡Ûí_§Úõl-;"PkÞÞÁQâ¼_Ñ^¢SŸx?"¸¦ùY騐ÒOÈ q’`~~ÚtËU¹CڒêV  I1Áß_ÿÙ`python-editor` is a library that provides the `editor` module for programmatically interfacing with your system's $EDITOR. Examples -------- ```python import editor commit_msg = editor.edit(contents="# Enter commit message here") ``` Opens an editor, prefilled with the contents, `# Enter commit message here`. When the editor is closed, returns the contents in variable `commit_msg`. ```python import editor editor.edit(file="README.txt") ``` Opens README.txt in an editor. Changes are saved in place. How it Works ------------ `editor` first looks for the ${EDITOR} environment variable. If set, it uses the value as-is, without fallbacks. If no $EDITOR is set, editor will search through a list of known editors, and use the first one that exists on the system. For example, on Linux, `editor` will look for the following editors in order: * vim * emacs * nano When calling the `edit()` function, `editor` will open the editor in a subprocess, inheriting the parent process's stdin, stdout