kagevf

I used it recently because it's the built-in scripting option for Outlook. I found myself writing the same emails over and over again, so I automated the writing with VBA, using input prompts for the variable parts. I'm not familiar with the available objects, so leaned heavily on chat gpt for that. Associated the script with a macro, then linked to a menu button and now I can quickly compose an email with a shortcut key.

The name is misleading. The document omits the part about executing top level forms. It does mention compiling them, though:

"[...] Compile the current toplevel form.

With (positive) prefix argument the form is compiled with maximal debug settings (‘C-u’). With negative prefix argument it is compiled for speed (‘M--’). If a numeric argument is passed set debug or speed settings to it depending on its sign."

> C-x C-e

> C-M-x

I use the first 2 keybindings you mention only with emacs lisp; the other 3 I had to look up.

I get a lot of milage from these:

  C-c C-c ;; slime-compile-defun
  C-c C-k ;; slime-compile-and-load-file
  C-c C-j ;; slime-eval-last-expression-in-repl
  C-c C-y ;; slime-call-defun

... with C-c C-c probably the one I use the most, and it's pretty easy on the hands.

> The quote is in the Preface, which is outside of the book itself.

Thank you for pointing that out; I'll read the whole thing in context.

I get the impression that the original quote from the book is using "name space" as it's used in other languages outside of CL, except that the book is from 1992 so not sure if that usage was widespread yet - maybe in C++? But it's almost like they wanted to say "a package is analogous to a name space as it's used in [algol-derivative]." Definite potential for confusion there, since "namespace" has a very specific meaning in CL and in general helps explain the difference between Lisp-1 and Lisp-2 (Lisp-n) varieties.

I put that sentence into a "scratch.txt" and a .org buffer in emacs, and when I hit M-e (forward-sentence) it just goes to the end of the line ...

Then I realized that the 1st sentence was missing the extra space after the 2nd period, and then M-e jumped to the end of the first sentence.

In vim, hitting ) in normal mode stopped after each period.

It's an elixir framework, not the the shell in Alpine Linux ...

Reminds me of graphviz :)

Populating?

Hmmm ... nonsense apparently!

I got my iPad, tried several different apps, and I now see that the feature is present in all of the ones I tried.

I think what I did differently this time was hold the spacebar down long enough for the feature to kick in. On my android phone there isn't that long of a delay, so I think that's what threw me off.

Thank you for the correction!

> probably even from back in the pre-iPhone 4 days.

The first iPhone I got was a 3GS and it had the feature. The person at the apple store helpfully demonstrated it to me when I went to pick it up.

> I'm surprised more people don't know about this feature.

I have an iPad without that feature, and it's maybe 5 years old? I think it's a newer feature.

Also, in the past you could tap and hold on text and it would magnify the view around where you were tapping, but that feature was dropped at some point.

As we keep getting reminded on IRC, it's not the language that's fast, it's its implementation. After that, how it's used; minding space/time complexity - or not - impacts speed too.

> why wouldn't they?

Loss of institutional knowledge.

That was an informative read - thank you!

Ah, got it, thanks!

> the .d pattern

What's that? I ddg'd it and I got a bunch of hits for regex \d ...

Did they version the spreadsheets? Or maybe converted them to text and versioned the text format?

> It's odd how people could justify spending huge amounts on the hardware just to run the software, but didn't want to pay for the software

I wonder if the difference between capital expenditure vs operation expense was an influence . . .

> it imposes a greater cognitive requirement on the part of the developer

... because of the "monotonous" syntax? That was a reason mentioned by L Peter Deutsch in Coders at Work ...

Possibly. I should also note that the problem started happening after about 4 years of usage. I live in a hard water area, but use a water softener.

Maybe what you said is a clue, though, and I’ll see if I can find any information phrased in terms of soap reacting with water. Different variations of “soap doesn’t drain” hasn’t found me any hits, like I’m the only one having this issue.

I have a dishwasher that seems to work fine, except that after it's done it's still filled with soap bubbles. The water has drained, but not the soap. Dishwasher repair person looked at it, suggested replacing the motor, but that didn't work. The repair person even called the manufacturer, but the manufacturer didn't know what was wrong either.

I have no idea what the problem is ... for now, I've been washing in the sink and drying with a dish dryer from Japan (shokki kansouki).

So, I know that elisp has historically lacked lexical scope, so setting variables without a prefix has the potential for name clashes since even a variable setq'd into existence inside a defun will be added to the global namespace.

I did an experiment to double check it's still true in a recent-ish emacs:

  (defun my-fun ()
    (setq test-123-456 'this-is-a-test))

  (my-fun)

  test-123-456 => this-is-a-test

There is some information in the info file under elisp about lexical binding, but you can just use let to keep variables in a lexical scope.

  (defun my-other-fun ()
    (let ((test-789 'this-is-another-test))
      test-789))

  (my-other-fun)

  test-789 => *** Eval error ***  Symbol’s value as variable is void: test-789

Recently, I read about someone who basically had a single running image and it would dispatch to the right function based on the command names sent to it, and the image was running swank, which sounded like a neat idea. I saw it in a comment, either here or on reddit ...

It seems to be more of a spectrum in Lisps, spanning from syntax enhancements to full blown languages.

> Besides the infamous Javascript framework churn

reactjs came out in 2013, so it meets the 10y metric, but it has some internal churn, such as classes, hooks, etc

In TFA: "Also, .US domains are only supposed to be available to U.S. citizens and to those who can demonstrate that they have a physical presence in the United States."

... and ...

"Under NTIA regulations, the administrator of the .US registry must take certain steps to verify that their customers actually reside in the United States, or own organizations based in the U.S. But Interisle found that whatever GoDaddy was doing to manage that vetting process wasn’t working."

> Double quote and then 9?

Interesting ... I checked the help using :h " and got to the bottom of it.

So "0 is the most recent thing you copied - I use that all the time, it's very useful. Including ctrl-r 0 in insert mode.

The other numbers 1 - 9 are the last thing that were cut either from a delete or a change, where "1 is the most recent, "2 the next recent, and so on.

The trick, though, is that it has to be //more than 1 line// to automatically end up in a numbered register - unless you explicitly use a numeric register when cutting.

That feature comes from emacs; hit ctrl-y to get ("yank") the last thing you copied, hit alt-y to get the previous thing you copied, and keep hitting alt-y in succession to cycle through the clipboard, which is called the "kill ring" in emacs.

I don't know if vim itself supports that feature, let alone vi mode on the command line. "Real" vim supports adding text to registers - does vi mode support it?

I don't recall if they actually used "Klondike", but I'm gathering as much based on the other comments.