Lines Matching +full:ascii +full:- +full:based
7 ---
9 These days most developers use ``git send-email`` instead of regular
19 -------------------
23 attachments, but then the attachments should have content-type
44 Emailed patches should be in ASCII or UTF-8 encoding only.
45 If you configure your email client to send emails with UTF-8 encoding,
48 Email clients should generate and maintain "References:" or "In-Reply-To:"
51 Copy-and-paste (or cut-and-paste) usually does not work for patches
54 copy-and-paste.
66 -----------------------------
75 - TUI = text-based user interface
76 - GUI = graphical user interface
85 - :menuselection:`Do Not Send Flowed Text` must be ``enabled``
86 - :menuselection:`Strip Whitespace Before Sending` must be ``disabled``
89 should appear, and then pressing :kbd:`CTRL-R` let you specify the patch file
97 To insert a patch use :menuselection:`Message-->Insert File` (:kbd:`CTRL-I`)
102 :menuselection:`Configuration-->Preferences-->Compose-->Wrapping` should be
111 from :menuselection:`Format-->Paragraph Style-->Preformatted` (:kbd:`CTRL-7`)
115 :menuselection:`Insert-->Text File...` (:kbd:`ALT-N x`)
118 You can also ``diff -Nru old.c new.c | xclip``, select
130 disadvantage is any text you type in the email will not be word-wrapped
134 word-wrapped and you can uncheck "word wrap" without losing the existing
137 At the bottom of your email, put the commonly-used patch delimiter before
138 inserting your patch: three hyphens (``---``).
154 as inlined text will make them tricky to extract from their 7-bit encoding.
164 if it was properly composed. Emails are saved as read-write for user only so
196 before middle button or shift-insert or use::
203 You can also generate patches with ``git format-patch`` and then use Mutt
206 $ mutt -H 0001-some-bug-fix.patch
213 set send_charset="us-ascii:utf-8"
236 set charset = UTF-8 # value of $LANG; also fallback for send_charset
237 # Sender, email address, and sign-off line must match
245 https://gitlab.com/muttmua/mutt/-/wikis/UseCases/Gmail
259 - ``quell-flowed-text`` is needed for recent versions
260 - the ``no-strip-whitespace-before-send`` option is needed
266 - Works well for inlining text (or using attachments).
267 - Allows use of an external editor.
268 - Is slow on large folders.
269 - Won't do TLS SMTP auth over a non-SSL connection.
270 - Has a helpful ruler bar in the compose window.
271 - Adding addresses to address book doesn't understand the display name
283 - Allow use of an external editor:
290 - "External Editor Revived"
292 https://github.com/Frederick888/external-editor-revived
294 https://addons.thunderbird.net/en-GB/thunderbird/addon/external-editor-revived/
298 https://github.com/Frederick888/external-editor-revived/wiki
300 - "External Editor"
306 :menuselection:`View-->Toolbars-->Customize...`
312 editor. Most notably if you are using gvim then you must pass the -f
313 option to gvim by putting ``/usr/bin/gvim --nofork"`` (if the binary is in
320 - Edit your Thunderbird config settings so that it won't use ``format=flowed``!
322 :menuselection:`Main Menu-->Preferences-->General-->Config Editor...`
325 - Set ``mailnews.send_plaintext_flowed`` to ``false``
327 - Set ``mailnews.wraplength`` from ``72`` to ``0``
329 - Don't write HTML messages! Go to the main window
330 …:menuselection:`Main Menu-->Account Settings-->youracc@server.something-->Composition & Addressing…
333 - Open messages only as plain text! Go to the main window
334 :menuselection:`Main Menu-->View-->Message Body As-->Plain Text`!
351 Another problem is that Gmail will base64-encode any message that has a
352 non-ASCII character. That includes things like European names.
357 HacKerMaiL (hkml) is a public-inbox based simple mails management tool that