Re: Pasting from the OS clipboard
Alexander Burger a...@software-lab.de writes: Hi Alex, - use the left/middle mouse button in an X11 session What's wrong with this? This is what seems the most natural way for me (in X11, or with GPM in a console window). There is nothing 'wrong' about it, but it would be nice to be able to just paste with C-y or C-v like usual. I always forget about it, try to paste like in Emacs, it doesn't work, then I have to go back and copy again with tmux or with the mouse and then paste in the REPL. I like e.g. how the Conkeror browser allows to copypaste from the keyboard, with the same keybindings like Emacs. So I almost forget that I'm not in Emacs all the time when doing some copypaste between Emacs and Conkeror. The same 'feeling' would be nice when changing between Emacs and the PicoLisp REPL. Would that be hard to implement? -- cheers, Thorsten -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Pasting from the OS clipboard
Hi Thorsten, - use the left/middle mouse button in an X11 session What's wrong with this? This is what seems the most natural way for me (in X11, or with GPM in a console window). There is nothing 'wrong' about it, but it would be nice to be able to just paste with C-y or C-v like usual. I always forget about it, try to Ah, yes, understand. Would that be hard to implement? Not sure. Does anybody know where emacs stores its clipboard? If it is a file (or accesible via some well-defined mechanism), it would be easy. I suspect this is not the case (?). ♪♫ - Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Bug in (env)?
Hi Alex, in the newest testing version on 64bit Archlinux PicoLisp terminates when I call (env) without args. A bug? ,--- | : (env) | Speicherzugriffsfehler | $ `--- -- cheers, Thorsten -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Bug in (env)?
Hi Thorsten, in the newest testing version on 64bit Archlinux PicoLisp terminates when I call (env) without args. A bug? Yes, indeed! 'env' crashed when called at the top level (i.e. without any existing bindings). Same for 'trail' and 'up'. The bug was introduced recently by a check for debug break. I fixed it, and uploaded a new testing version. Many thanks for the hint! ♪♫ - Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: New Article about 'for'
Joe Bogner joebog...@gmail.com writes: Hi Joe, Great article! Thank you for sharing. I spent a bit of time trying to figure out how to use 'for' when I started. The article would have been very helpful then. thanks, I just added a section to the 'Help' page in the Wiki (http://picolisp.com/5000/!wiki?Help) that describes the 'PicoLisp Wiki Mode' for Emacs. With this mode, writing articles for the Wiki in Emacs becomes very fast and convenient. You can find the picolisp-wiki-mode.el file in the 'lib/el/' folder of the testing release. -- cheers, Thorsten -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Normalize PicoLisp Wiki Syntax
Hi List,
when writing the picolisp-wiki-mode for Emacs, I began to understand why
mark-up syntax is usually symmetric, i.e. the end-tag looks like a
180° mapping of the start-tag (e.g. the JSP Scriplet % ... %).
This makes parsing the file and constructing regexp much easier, because
its always clear which end-tag belongs to which start-tag.
The PicoLisp Wiki Syntax does not follow this convention:
,---
| 3{Heading} Heading (level 3)
|Levels 1 .. 6 are allowed
|
| {3} Insert 3 line breaks
| {-3} Insert 3 line breaks, clear float style
|
| /{italic} Italic font
| !{bold}Bold font
| _{underline} Underlined font [...]
`---
Considering the possible nesting of elements (e.g. a bold word inside a link
inside a list item), it becomes very difficult to construct regexp that
reliably identify elements (necesary for fontification) because there
are so many closing braces '}' around (and there might even be closing
braces in the text itself).
What about changing the syntax to this:
,---
| 3{Heading}3 Heading (level 3)
|Levels 1 .. 6 are allowed
|
| {3} Insert 3 line breaks
| {-3} Insert 3 line breaks, clear float style
|
| /{italic}/ Italic font
| !{bold}!Bold font
| _{underline}_ Underlined font [...]
`---
I know, its one more char to type (not when you use the
picolisp-wiki-mode for Emacs) and looks ugly, but would make things a
bit more 'standard' and easier to deal with. Its not really a big issue,
since the picolisp-wiki-mode works fine even if fontification is a bit
random. Don't know if it would be an improvement and worth the pain.
--
cheers,
Thorsten
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Normalize PicoLisp Wiki Syntax
On Sat, 24 Nov 2012 17:29:13 +0100
Thorsten Jolitz tjol...@googlemail.com wrote:
Hi List,
when writing the picolisp-wiki-mode for Emacs, I began to understand
why mark-up syntax is usually symmetric, i.e. the end-tag looks like a
180° mapping of the start-tag (e.g. the JSP Scriplet % ... %).
This makes parsing the file and constructing regexp much easier,
because its always clear which end-tag belongs to which start-tag.
The PicoLisp Wiki Syntax does not follow this convention:
,---
| 3{Heading} Heading (level 3)
|Levels 1 .. 6 are allowed
|
| {3} Insert 3 line breaks
| {-3} Insert 3 line breaks, clear float
style |
| /{italic} Italic font
| !{bold}Bold font
| _{underline} Underlined font [...]
`---
Considering the possible nesting of elements (e.g. a bold word inside
a link inside a list item), it becomes very difficult to construct
regexp that reliably identify elements (necesary for fontification)
because there are so many closing braces '}' around (and there might
even be closing braces in the text itself).
What about changing the syntax to this:
,---
| 3{Heading}3 Heading (level 3)
|Levels 1 .. 6 are allowed
|
| {3} Insert 3 line breaks
| {-3} Insert 3 line breaks, clear float
style |
| /{italic}/ Italic font
| !{bold}!Bold font
| _{underline}_ Underlined font [...]
`---
I know, its one more char to type (not when you use the
picolisp-wiki-mode for Emacs) and looks ugly, but would make things a
bit more 'standard' and easier to deal with. Its not really a big
issue, since the picolisp-wiki-mode works fine even if fontification
is a bit random. Don't know if it would be an improvement and worth
the pain.
It's not an improvement, and not worth it, imo. The current wiki syntax
is pretty much a lightweight variant of TeX, Emacs can fontify TeX just
fine, so the issue is in the emacs mode, not the syntax.
-Jose
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Normalize PicoLisp Wiki Syntax
José Romero j...@2.71828.com.ar writes: It's not an improvement, and not worth it, imo. The current wiki syntax is pretty much a lightweight variant of TeX, Emacs can fontify TeX just fine, so the issue is in the emacs mode, not the syntax. It does look pretty ugly, I agree, and I wasn't sure myself if it would be such a good idea. It would make some things easier, but these things are not impossible with the current syntax either. Thanks for the feedback, I think you are right. -- cheers, Thorsten -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Wiki recent changes
An important common feature of wikis is the ability to see recent changes. I briefly looked and didn't see it on the picolisp wiki. Did I miss it? If not, would it be much to add? I can attempt a patch or will gladly defer to someone else. Just a thought. Thanks! I've been missing that feature too. /Jon -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
