281–290 of 340 posts
Earlier quoted context omitted.
What? I'm not trying to, I'm trying to be funny. Sorry if you read it in your head differently.
> Don't be stupid, stop saying stupid shit like "python instead of lisp".
Earlier quoted context omitted.
I have never figured out how to get a good font and rendering going for text in Urdu/arabic script.
Is vscode better at Urdu/arabic?
I did setup Obsidian for a friend to write in Urdu, and that worked almost perfectly modulo some minor stuff.
Earlier quoted context omitted.
> Don't be stupid, stop saying stupid shit like "python instead of lisp".
Well, that is a stupid thing to say. You probably just haven't yet realized why.
Earlier quoted context omitted.
I do understand that for you Emacs is a Lisp development environment first, not a text editor. Can you imagine people enjoying the user experience of Emacs while simultaneously preferring languages that are not Lisp?
> I do understand that for you Emacs is a Lisp development environment first It's not "for me", it is what it is. Emacs first and foremost is a Lisp machine, with a text-editor built into it, not the other way around, it's not a text-editor that uses Lisp as its configuration language. "user experience of Emacs" is to be able to send any expression and sub-expression without any preceding ceremony directly to the REP…
Earlier quoted context omitted.
> - Implement better sandboxing and security measures for extensions. Why, pray tell, should this be of any concern at all? Sandboxing is used when the host is concerned about running programs that he doesn't trust. There is no reason that an Emacs package would require security measures around it, unless it were knowingly potentially malware. The only reality in which I could see this is if people were using proprie…
> Sandboxing is used when the host is concerned about running programs that he doesn't trust. Trust? Trusting criminals doesn't stop them from committing crime. You may trust your emacs color theme author. Pretty colors from an innocent artist. You run the theme code without any sandboxing. Everything is going well. Then the author adds a keyloger, project code scrapper, and phone-home feature in his theme. You updat…
> You update all your emacs packages automatically without any code review. Then you start getting emails from your companies security team asking why you uploaded sensitive projects to a 3rd party.
If you do not trust the author or maintainers of a random program and refuse to review any code updates before installing it, then you are a moron.
I think if there is a concern that people would upload malicious packages, then there would be a level of trust put into the repositories that accept and offer them to review submissions before accepting them. This is still imperfect, but it shifts some responsibility off of you.
> Wouldn't it make more sense to restirct color themes to color and font related tasks? Why should a color theme be allowed to scrape sensitive code from your disk and upload it to a 3rd party without your consent?
Why SHOULDN'T a color theme be allowed to scrape code from your disk? Maybe the color theme is sophisticated enough to want to do that, or talk to some network. Something like a seasonal color theme that responds to the local weather might have a lot of hack value; and that is precisely the point you are missing. Emacs is not about restricting what you can and can't do, because the designers of Emacs understand that restricting what the user is allowed to do ultimately hinders freedom and creativity. It is one of the very few platforms left that's still like that, and I believe it should stay that way. If people want to use an editor that's very safe and tells them what to do rather than vice versa, then they should probably consider VS Code, or something like it which DOES upload your data to a third party without your consent, because it is smarter and knows better than you what you should be doing with your computer.
Earlier quoted context omitted.
The solution to "this text editor takes too long to start up" is poorly addressed by the solution to "just leave it running in the background all the time".
It's not a "solution"; you still need to solve your undesirably slow startup, but if you're having to kill and restart Emacs multiple times a day, something is wrong with your workflow. Normally, Emacs doesn't require restart - for weeks and months in some cases. emacsclient is useful on its own. For example, I use it to edit just about any text, in any input box in any app, delegating the task to Emacs, or when I wa…
Earlier quoted context omitted.
I still don’t understand what advising has to do with homoiconicity. When you advise a function in emacs you’re not traversing its code as data, you’re adding some code to run at a predefined hook like :before, :after, etc., and I don’t see any reason why you couldn’t write a python interpreter that also lets you do the same thing. You could also have a repl implemented on top of this interpreter in python itself and…
Right, advising itself on the surface doesn't seem to be inherently tied to homoiconicity, here's the concrete example in Elisp, this would print how long it took to evaluate a form. (defun add-timing-advice (orig-fun &rest args) (let ((start-time (current-time))) (prog1 (apply orig-fun args) (message "Evaluation took %f seconds" (float-time (time-subtract (current-time) start-time)))))) (advice-add 'eval-print-last-…
Earlier quoted context omitted.
It's not a "solution"; you still need to solve your undesirably slow startup, but if you're having to kill and restart Emacs multiple times a day, something is wrong with your workflow. Normally, Emacs doesn't require restart - for weeks and months in some cases. emacsclient is useful on its own. For example, I use it to edit just about any text, in any input box in any app, delegating the task to Emacs, or when I wa…
This has strong "you're holding it wrong" energy.
Earlier quoted context omitted.
Well, that is a stupid thing to say. You probably just haven't yet realized why.
You're just so full of yourself, aren't you? You know the one true way to do programming, it's lisp and everyone else is an idiot? This was old before you were even born.
Earlier quoted context omitted.
> I do understand that for you Emacs is a Lisp development environment first It's not "for me", it is what it is. Emacs first and foremost is a Lisp machine, with a text-editor built into it, not the other way around, it's not a text-editor that uses Lisp as its configuration language. "user experience of Emacs" is to be able to send any expression and sub-expression without any preceding ceremony directly to the REP…
Between this and you calling me stupid - twice! I now understand enough about you to ignore you and feel good about that decision. Thank you.