diff options
| -rw-r--r-- | content/blog/105_sieve.md | 19 | ||||
| -rw-r--r-- | plugins/read_time/read_time.py | 3 |
2 files changed, 19 insertions, 3 deletions
diff --git a/content/blog/105_sieve.md b/content/blog/105_sieve.md new file mode 100644 index 0000000..533ff72 --- /dev/null +++ b/content/blog/105_sieve.md @@ -0,0 +1,19 @@ +Title: Don't fear the sieve +Category: Blog +Tags: /dev/diary, e-mail, programming +Date: 2019-02-01 +Slug: understanding-sieve +Status: Draft + +If you don't already know, sieve (/siːv/) is an e-mail filtering language. +It's not touring complete (i.e. it doesn't allow recursion) +and has been defined through a series of RFCs for the base language +as well as several extentions. + +The RFCs aren't exactly nice to read. +But luckily, there are plenty of tutorials on the internet, +that try to explain sieve. +Unfortunately most of them are garbage. + +The main reason for this is, that the articles never deal +with a realistic set of constraints of requirements diff --git a/plugins/read_time/read_time.py b/plugins/read_time/read_time.py index 14139a7..ccd4a07 100644 --- a/plugins/read_time/read_time.py +++ b/plugins/read_time/read_time.py @@ -63,15 +63,12 @@ def calculate_wpm(text, data, language): for word in text.split(' '): if '<skip>' in word: skipping = True - print("Starting to skip") if not skipping: new_text += word + ' ' - print("Word: ", word) if '</skip>' in word: skipping = False - print("Ending skipping") read_time = len(new_text.split(' ')) / wpm |