Live data from Hacker News

Build Your Own Text Editor

viewsourcecode.org

141–150 of 164 posts

Re: Build Your Own Text Editor

#141

Reference implementations of medium sized applications are incredibly useful for leveling up as a programmer. While there are many large successful open source applications, many are overwhelming to read and learn from. Having something that outlines the key features and components and which ignores the important but complicated edge cases assists in keeping the attention focused. Now if there are annotation within t…

Wholeheartedly agree. Making my own lisp was an eye opener on how programming languages work - and that's after I've read a lot of theory on the matter. By the way, is there are similar resource for building your own relational SQL-based database?

Maybe peek at H2? http://h2database.org

Re: Build Your Own Text Editor

#142
post #33

I'm curious if anyone here regularly codes in a text editor they wrote themselves? I've often thought of coding one for fun, with no intention to share it, just for the purpose of having a long-term project that evolves along with my skills. I've never made time for it, but I still consider it once in a while.

I wrote one back in 1984-85 that I called QEdit, and have been using and updating it ever since.

QEdit FTW! Thank you! It was my go to editor for ages. Used it to write all my AutoCAD shareware.

It took me forever to unlearn the Wordstar key bindings.

I'll have to look it up.

Re: Build Your Own Text Editor

#143
post #140

Earlier quoted context omitted.

I used to ~20 years ago. It was a curses-based mini-emacs in C; the fun part was a notebook-style interface to a Forth-like language I added in. Eventually I wanted the same kind of interface for Python programming in Emacs, and moved on to that with https://github.com/darius/halp .

I just tried halp, it seems pretty cool, thank you for making it available!

You're welcome! It does hardly anything compared to systems like IPython, but I'm reluctant to learn interfaces.

Re: Build Your Own Text Editor

#144

Earlier quoted context omitted.

It's pretty weird to see "correct" justified by calling the opposite "poor taste". We're talking about a mismatch between a style of code and certain tools; a better answer is to use tools that work well with the style of code you like.

It's not just tooling. The more complex the expression, the more likely it would aid in understanding if you gave it a name.

I agree that naming expressions often helps understanding, and that's worthwhile -- I guess I just disagree about this code at first glance. Maybe if I tried to delve into it.

Re: Build Your Own Text Editor

#145
post #35
post #29

Earlier quoted context omitted.

Do you have general programming experience?

Yep, lots of Ruby/PHP/Python/Javascript, some Java. So I can comfortably read syntax in most languages, but obviously none of the languages I've used are as low level as C.

Yeah, brush up on pointers a tad bit (just have a look at some youtube videos, honestly), if you are uncomfortable with them, and then you should be good to go.

Re: Build Your Own Text Editor

#146

Reference implementations of medium sized applications are incredibly useful for leveling up as a programmer. While there are many large successful open source applications, many are overwhelming to read and learn from. Having something that outlines the key features and components and which ignores the important but complicated edge cases assists in keeping the attention focused. Now if there are annotation within t…

I found that another hard thing that feels like a prerequisite for leveling up further is getting the feel for design/architecture of medium-sized systems. There's a pretty awesome resource for that particular need - the series of books called "The Architecture of Open Source Applications". http://aosabook.org/en/index.html (The books are CC and free to read on-line :)) I'm just through the few first chapters of the…

Both, the tutorial and the aosabook are very, very, helpful ressources. We certainly need more like that.

Re: Build Your Own Text Editor

#147
post #69

marginally relevant: I was looking for a terminal text editor for git commits and other similarly simple tasks: my only requirement is that I can save&leave with ^D. Any suggestions?

Emacs?

    (global-set-key (kbd "C-d") 'save-buffers-kill-terminal)

Re: Build Your Own Text Editor

#150

Earlier quoted context omitted.

I wrote one back in 1984-85 that I called QEdit, and have been using and updating it ever since.

QEdit FTW! Thank you! It was my go to editor for ages. Used it to write all my AutoCAD shareware. It took me forever to unlearn the Wordstar key bindings. I'll have to look it up.

Thanks for the kind words. I was forced to change the name a few years back (1992) - it is now called TSE, or The Semware Editor.

Unlearn Wordstar key bindings? Isn't that sacrilege? :-)

Post reply on HN