unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: unable to create/find a .cpp file (ed.2)
Date: Tue, 01 Aug 2006 09:18:19 -0600	[thread overview]
Message-ID: <eanrcp$f71$1@sea.gmane.org> (raw)
In-Reply-To: <874px1pk4l.fsf@localhost.localdomain>

Gary Wessle wrote:
> Hi
> 
> after my first post, I here provide more info in-order to find a fix.
> thank you for giving me your time to fix my problems.
> 
> 
> ################ from old post ################
> ctl-xf which does find/create a file then I type test.cpp then I get this in
> the echo area
> ****************************************************************
> File is opened with an external viewer. See buffer *extview log* for status messages.
> ****************************************************************
> 
> in *extview log* I have
> ****************************************************************
> Opening file ~/test.cpp with handler: more '%s'
> /home/fred/test.cpp: No such file or directory
> 
> Process extview-process finished
> ****************************************************************
> 
> ################ more info ################
> C-h v extview-application-associations'
> (("\\.py$")
>  ("\\.pdf$" . "xpdf %s"))
> 
> C-h f mailcap-parse-mimetypes function does not have any ".cpp" entry:

Yes, but did you check each of the files listed in that function's
doc string?  That is where the ".cpp" -> "more '%s'" association must
be coming from since it's not in extview-application-associations.

But I think you could override the mailcap/mimetypes association like
this:

(setq extview-application-associations
       (cons '("\\.cpp\\'" . nil) extview-application-associations))

> $emacs -q --no-site-file (the problem goes away)
> $emacs -q (the problem DOES NOT returns)

That means the source of the problem is either ~/.emacs or default.el,
but we already know it's just because you're loading the extview library
from ~/.emacs.

-- 
Kevin

  reply	other threads:[~2006-08-01 15:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-28 20:08 unable to create/find a .cpp file (ed.2) Gary Wessle
2006-08-01 15:18 ` Kevin Rodgers [this message]
     [not found] ` <mailman.4735.1154445579.9609.help-gnu-emacs@gnu.org>
2006-08-02 16:13   ` Gary Wessle
2006-08-02 16:29     ` Gary Wessle
2006-08-02 17:48       ` Kevin Rodgers
     [not found]       ` <mailman.4765.1154541341.9609.help-gnu-emacs@gnu.org>
2006-08-02 23:52         ` Gary Wessle
2006-08-03 13:31           ` Kevin Rodgers
2006-08-02 17:46     ` Kevin Rodgers
     [not found]     ` <mailman.4764.1154540943.9609.help-gnu-emacs@gnu.org>
2006-08-03 17:48       ` Gary Wessle
2006-08-04  2:19         ` Kevin Rodgers
     [not found]         ` <mailman.4831.1154658014.9609.help-gnu-emacs@gnu.org>
2006-08-04  6:35           ` Gary Wessle
2006-08-04 13:55             ` Kevin Rodgers
     [not found]             ` <mailman.4850.1154699821.9609.help-gnu-emacs@gnu.org>
2006-08-05  0:22               ` Gary Wessle

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='eanrcp$f71$1@sea.gmane.org' \
    --to=ihs_4664@yahoo.com \
    /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.
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).