From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: unable to create/find a .cpp file (ed.2)
Date: Thu, 03 Aug 2006 07:31:32 -0600 [thread overview]
Message-ID: <eastsg$5mo$1@sea.gmane.org> (raw)
In-Reply-To: <874pwu66hh.fsf@localhost.localdomain>
Gary Wessle wrote:
> Kevin Rodgers <ihs_4664@yahoo.com> writes:
>
>> Gary Wessle wrote:
>>> Gary Wessle <phddas@yahoo.com> writes:
>>>
>>>> Kevin Rodgers <ihs_4664@yahoo.com> writes:
>>>>> But I think you could override the mailcap/mimetypes association like
>>>>> this:
>>>>>
>>>>> (setq extview-application-associations
>>>>> (cons '("\\.cpp\\'" . nil) extview-application-associations))
>>>>>
>>>> yes, that fixed it, thank you.
>>> sorry, that fix just above will let me open an existing .cpp file but
>>> will not let me create a new one. as well as it will fail find/create
>>> .h files
>> Exactly what happens when you try to visit a new .cpp file?
>>
>> --
>> Kevin
>
> sorry, I meant to say, I can visit a new .cpp file fine now but
> visiting a new file.h I get in the *extview log*
>
> Opening file ~/myPrograms/backtest/man.h with handler: more '%s'
> /home/fred/myPrograms/backtest/man.h: No such file or directory
>
> Process extview-process finished
>
> ****************************************************************
>
> I thought to add a bit extra to what you suggested by doing in my
> .emacs the following
>
> (setq extview-application-associations
> (cons '("\\.cpp\\'" . nil) extview-application-associations),
> (cons '("\\.h\\'" . nil) extview-application-associations))
>
> and then restart emacs and trying to visit a new .h file but I still
> get the same error i.e, adding the .h line above to my .emacs did
> nothing.
Your MIME configuration is broken, not Emacs. Check ALL the mime.types
files I listed for you. It seems there is a default entry that maps
every file extension to the more '%s' command; you could verify that
by visiting a file with a nonsensical extension, e.g. "abc.foobarbaz".
--
Kevin
next prev parent reply other threads:[~2006-08-03 13:31 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
[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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='eastsg$5mo$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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.