I happened to have 2h free, so I decided to write a text adventure game engine with #chickenscheme. Lisps still are really fun languages, and #paredit in #emacs is awesome!
#chickenscheme #paredit #emacs #scheme
Spending a lot of time in Scheme. I think I'm finally at the point where retraining my fingers to use paredit makes sense. My first attempts spiraled into swearing sessions since it doesn't let you unbalance parens. I get why it does this but it was a bit much while trying to get used to sexps.
#programming #emacs #lisp #scheme #guile #paredit
You can have some of #paredit powers in other languages with #puni : https://github.com/AmaiKinono/puni #emacs
Emailed the #paredit author and it is a known issue. Workaround is to undefine the bindings for RET and C-j in paredit-mode-map:
(define-key paredit-mode-map (kbd "RET") nil)
(define-key paredit-mode-map (kbd "C-j") 'paredit-newline)
Emailed the #paredit author and it is a known issue. Workaround is to undefine the bindings for RET and C-j in paredit-mode-map:
(define-key paredit-mode-map (kbd "RET") nil)
(define-key paredit-mode-map (kbd "C-j") 'paredit-newline)
Yesterday I activated #paredit by mistake, thinking it was show-paren-mode, and today I find this. I think I'll have to learn it :BlobCatGoogly:
Paredit 25 released, after 8 years | Hacker News
Yesterday I activated #paredit by mistake, thinking it was show-paren-mode, and today I find this. I think I'll have to learn it :BlobCatGoogly:
Paredit 25 released, after 8 years | Hacker News
#EmacsTip: You can use anything to edit any code. But every Lisp #hackers (not crackers) know that one thing must be used. Can you guess what it is?
It's #Paredit! Be it #Lisp, #EmacsLisp, #Scheme or #CommonLisp, #Paredit will always keep away those "unmatched parentheses" errors. A must use package for editing files with parentheses, braces and brackets. Available from #NonGNUELPAdevel.
#emacstip #hackers #paredit #lisp #emacslisp #scheme #commonlisp #NonGNUELPAdevel #emacs #parens #Parentheses #braces #brackets
gosh dangit i wanna use #paredit and #emacs on the console.
and i mean, i /do/, and have been for ages, but...
C-<space> does not work on the 'dvorak-programmer' layout.
also C-left/right and C-M-left/right can't slurp/barf because it thinks I'm trying to switch to another TTY.
lots of problems and like, I've gotten used to flat out /ignoring/ them, but I probably shouldn't do that...
I feel a bit spoiled implementing my compiler in #racket. Still very early of course (only spent two short evening sessions with it) but it feels like I get a lot done with not a lot of code or time.
It's a shame that I'll probably have to drop racket eventually to cut down compile times to what I want.
Main thing slowing me down is that I'm trying to see what it's like to use #acme instead of #emacs (#paredit is completely OP)
Me: "Yeah I use #paredit. If you write Lisp, you gotta have pardit!"
Also me: *disables paredit every time my parens aren't matching so I can manually adjust them*