google-api-python-client VS GNU Emacs

We uploaded one of Google’s sample Python scripts to Docuwriter to test some of the code documentation types, starting with General Documentation:

Google has documentation and 'getting started' resources for the GMail API, but the sample script implemented in their 'Python Quickstart' guide is using syntax that is documented separately in the Google API Python Client docs and GMail API docs.

First hit on google: https://github.com/googleapis/google-api-python-client/issues/1640

I'd recommend using one of the clients vs trying to assemble the requests yourself. The Python client is a good place to start.

The main functionality is handled by the Thermostat class. On creation it creates a service object using the Google Python API Client. That's used later to help build and execute API requests. At app exit the service object is closed.

At first, to simplify the procedure, I started with the credentials of an open source email client. I then used the tool mutt_oauth2.py (which is a streamlined version of google-api-python-client).

Based on my understanding, this is now only possible via through OAUTH2. After several failed attempts, it seems I found the official supported library, that is google-api-python-client.

API client for Python

Documentation. I've encountered several non documented requirements on various services that are just frustrating for no reason, until you find the correct answer on StackOverflow or GitHub. This can be a known issue that is unfixed for years, even though it's only a change in documentation. Again, Google's support teams keep claiming to file "internal bug reports" that go nowhere for years. Google is so busy always developing the "next big thing" that they forget to invest in their own existing tools that developers count on. See this example Issue from 2015 that was still gaining comments in 2021!

gnu.org - contains everything you need to research his philosophy.

stallman.org - personal website, contains a lot of opinion, but I absolutely respect this man in all what he says.

emacs.org (redirects to https://www.gnu.org/software/emacs/) - his non-philosophical work, one of two mainstream console text editors.

Forever, there was a file included in stock Emacs, `spook.el`, which could be hooked up to automatically add random strings of "interesting" keywords to each of your email or Usenet messages (in signatures, or in headers like `X-Spook`).

https://www.gnu.org/software/emacs/manual/html_node/emacs/Ma...

Looks like copyright date of 1988:

https://github.com/emacs-mirror/emacs/blob/master/lisp/play/...

https://github.com/emacs-mirror/emacs/blob/master/etc/spook....

Try `M-x spook RET` in an Emacs buffer.

If you want to spare a couple of detours, you probably could start with Emacs Org-mode according to Greenspun's eleventh rule: "Any sufficiently complicated PIM or note-taking program contains an ad hoc, informally specified, bug-ridden, slow implementation of half of Org mode."

Emacs: winget install GNU.Emacs

The whole cl-lib thing is a total disaster:

https://github.com/emacs-mirror/emacs/blob/master/lisp/emacs...

They added cl- as a prefix to each Common Lisp symbol.

FIRST is now called cl-first, CAAAR is now cl-caaar .

I would really prefer if GNU Emacs removes all Common Lisp functionality, instead of creating this really wacky stuff, with discussions about this topic every year.

Never too late to try! Take your time. Emacs will outlive us all. https://www.gnu.org/software/emacs/

GNU Emacs is a versatile, open-source text editor that offers extensibility and customization—a sort of self-documenting real-time display editor. Our thanks for the suggestion go to CartanAnnullator.

Emacs

Their DEFUN and DEFVAR macros for example let us define a function or a variable that will be available as a Lisp function, and can be used as an ordinary C function from the C code. Emacs is written in pure C99 language and works with both GCC and Clang I believe. We can just define a C function via macro, and it is auto exported and made available to Lisp. For example my first patch to Emacs was for this function (we added "count" argument to make it possible to skip enumerating files in a directory for the case when user code is just interesting if a directory is empty or not):