From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: face-at-point
Date: Fri, 14 Jun 2013 16:17:57 -0400 [thread overview]
Message-ID: <87mwqswioa.fsf@pierrot.dokosmarshall.org> (raw)
In-Reply-To: 87sj0k979j.fsf@gilgamesch.quim.ucm.es
Uwe Brauer <oub@mat.ucm.es> writes:
>>> "Nick" == Nick Dokos <ndokos@gmail.com> writes:
>
> > Uwe Brauer <oub@mat.ucm.es> writes:
> >> > The error is[fn:1]:
> >>
> >> I am sorry, this is also the fault of
> >> gnus-dired-attach
> >>
> >> Which by default uses this type of attachment, I have to look into it,
> >> how to change it on demand.
> >>
> >>
>
> > gnus-dired-attach uses mm-default-file-encoding to figure things out.
>
> I tried to generalize this function so that it optionally takes the type
> as an argument. Too complicated.
Eric Fraga has been prolific in providing solutions to these problems
today. In addition to the client side solution ("Use v instead of t")
which solves the problem on the recipient's side, he provided another
solution (which I have used in the past, but I forgot all about it until
I saw Eric's reply to your question in the gnus mailing list) that
solves the problem on the sender's side: let gnus-dired-attach default
to whatever it bloody well pleases - the attachment cookie it inserts in
the mail you are composing is just text (until you hit C-c C-c and then
it becomes a "real" attachment), so if the type is not to your liking,
you can go ahead and edit it at will (I've stripped out parts of the
cookie, so it won't be mistaken as a real attachment - I'm not sure
how to quote it so that it won't be recognized):
... type="application/octet-stream" filename="~/Desktop/foo" disposition=attachment description=Hunoz>
to
... type="text/plain" filename="~/Desktop/foo" disposition=attachment description=Hunoz>
Another instance of the "Your life in plain text" principle.
I thought I'd post a note with Eric's solution here, just to close the
loop all the way. Here is a reference to his reply:
http://thread.gmane.org/gmane.emacs.gnus.general/83319/focus=83320
Thanks, Eric!
--
Nick
next prev parent reply other threads:[~2013-06-14 20:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 8:17 serious problems with org-8 under Xemacs-21.5.32 Uwe Brauer
2013-06-14 9:32 ` Nick Dokos
2013-06-14 10:40 ` face-at-point (was: serious problems with org-8 under Xemacs-21.5.32) Uwe Brauer
2013-06-14 12:21 ` face-at-point Nick Dokos
2013-06-14 12:31 ` face-at-point Nick Dokos
2013-06-14 13:00 ` face-at-point Uwe Brauer
2013-06-14 20:17 ` Nick Dokos [this message]
2013-06-14 20:55 ` face-at-point Eric S Fraga
2013-06-14 21:18 ` face-at-point Uwe Brauer
2013-06-14 22:32 ` face-at-point Nick Dokos
2013-06-15 11:45 ` face-at-point Michael Sperber
2013-06-14 11:06 ` [partically solved] (was: serious problems with org-8 under Xemacs-21.5.32) Uwe Brauer
2013-06-14 15:00 ` serious problems with org-8 under Xemacs-21.5.32 Eric S Fraga
2013-06-14 16:23 ` Nick Dokos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mwqswioa.fsf@pierrot.dokosmarshall.org \
--to=ndokos@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).