cdransf/coryd.dev-eleventy
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix: myriad typos and issues

Browse source
This commit is contained in:
Cory Dransfeldt 2023-05-06 17:33:00 -07:00
parent 21a158602a
commit be92f3bdf0
No known key found for this signature in database
64 changed files with 107 additions and 104 deletions
Download patch file Download diff file Expand all files Collapse all files

6
src/posts/2022/automating-email-cleanup-in-gmail.md
View file

@ -7,7 +7,7 @@ tags: ['Gmail', 'automation']
Lately I've been leaning into automating the cleanup of email I receive in Gmail using a combination of Inbox-era categories that the application still exposes via search and [Google Apps Script](https://www.google.com/script/start/).<!-- excerpt -->
I wasn't using Gmail when Inbox was available (I'm sure I missed out) and know not all of the most beloved features have been migrated over to Gmail proper. That said, there _are_ some handy filters that didn't ascend to Gmail's tabbed inbox interface but are still available to create rules against[^1].
I wasn't using Gmail when Inbox was available (I'm sure I missed out) and know not all the most beloved features have been migrated over to Gmail proper. That said, there _are_ some handy filters that didn't ascend to Gmail's tabbed inbox interface but are still available to create rules against[^1].
I've created filter rules leveraging all of these legacy filters to automatically categorize messages the same way the current tabs do. These rules look like the following:
@ -88,7 +88,7 @@ The rules for deliveries and alerts operate in very much the same way, but with
'label:alerts -label:inbox'
```
Unrelated to cleanup, I also mark any unread emails in my archive as read, with this script running every minute using the `Time-driven` event source, `Minute timer` and is executed every minute (heavy-handed perhaps, but the error-rate for this has only been 0.02%):
Unrelated to clean up, I also mark any unread emails in my archive as read, with this script running every minute using the `Time-driven` event source, `Minute timer` and is executed every minute (heavy-handed perhaps, but the error-rate for this has only been 0.02%):
```javascript
function markArchivedAsRead() {
@ -105,5 +105,5 @@ function markArchivedAsRead() {
I have given some thought to refactoring my cleanup scripts such that the batch delete consumes an array of the individual search queries, iterating over them much like it does the threads it's operating on but, at that point, I'd be looking at a loop over the argument and then over the threads in a child loop when separate script functions can run without that being a concern.
[^1]: I am puzzled that Forums made the cut as a featured option.
[^2]: Don't email me via Feedbin. I'll miss it or it'll just be annoying.
[^2]: Don't email me via Feedbin. I'll miss it, or it'll just be annoying.
[^3]: I care when something ships, I don't care to reference the tracking info months later.