From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: unable to create a .cpp file
Date: Thu, 20 Jul 2006 16:33:30 -0600 [thread overview]
Message-ID: <e9p0ec$9ip$2@sea.gmane.org> (raw)
In-Reply-To: <20060720113712.5236.qmail@web54614.mail.yahoo.com>
Fred J. wrote:
> it is only when I comment this section below that the problem does not
> duplicate, but then I loose the functionality it provides.
> this section here is copied from the .emacs file below for easy of
> illustration
> ;; uncomment this section to associate pdf and python files with modes
> ;; opens a a file 'pdf' with xpdf and so on...
> (require 'extview)
> (push '("\\.pdf$" . "xpdf %s") extview-application-associations)
> (push '("\\.py$" . nil) extview-application-associations)
What does `C-h v extview-application-associations' tell you?
--
Kevin
next prev parent reply other threads:[~2006-07-20 22:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 3:56 unable to create a .cpp file Gary Wessle
2006-07-18 18:43 ` Kevin Rodgers
2006-07-18 21:22 ` Gary Wessle
2006-07-19 6:41 ` Gary Wessle
2006-07-19 10:28 ` Dieter Wilhelm
2006-07-20 11:37 ` Fred J.
2006-07-20 22:33 ` Kevin Rodgers [this message]
2006-07-19 16:15 ` Kevin Rodgers
2006-07-19 21:54 ` 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='e9p0ec$9ip$2@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).