From: Eliot Moss <moss@cs.umass.edu>
To: Fergus Daly <fergusd84@outlook.com>,
"'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: Re: Trouble with setting ini files : gnuplot and vi
Date: Mon, 21 Dec 2020 09:07:25 -0500 [thread overview]
Message-ID: <36027e5f-1240-8660-28c3-7e2aa855c2c8@cs.umass.edu> (raw)
In-Reply-To: <DB6PR03MB301372308688E730EC57E2F3A4C00@DB6PR03MB3013.eurprd03.prod.outlook.com>
On 12/21/2020 8:36 AM, Fergus Daly via Cygwin wrote:
> Despite best efforts I cannot find a way of setting user preferences for vi (e.g. preferred syntax-sensitive settings)
> and gnuplot (e.g. preferred line colours / thickness).
> I have tried editing /etc/vimrc, /etc/virc for vi; and /etc/X11/app-defaults/Gnuplot for gnuplot accordingly.
> (I use gnuplot-x11.) No change from standard representation.
> Any ideas?
The first thing I would check is whether you have an individual ~/.virc or ~/.gnuplot file that is
overriding the settings of interest. For gnuplot, at least, the man page says that its "show
loadpath" command will indicate where it looks for gnuplotrc. On my system that is
/usr/share/gnuplot/5.4/. Since my gnuplot offers x11 for "set term", I think I'm looking at the
right thing, but if gnuplot-x11 is truly different, then maybe try the "show loadpath" command for
it. I don't have vi installed (only vim) so I can't speak to that.
The next thing I would check are the various permissions, to make sure the program can actually read
the file(s) in question.
Maybe you have done all this, in which case I'm sorry my ideas were not helpful ...
Best wishes - Eliot Moss
next prev parent reply other threads:[~2020-12-21 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 13:36 Fergus Daly
2020-12-21 14:07 ` Eliot Moss [this message]
2020-12-21 20:58 ` Fergus Daly
2020-12-21 21:02 ` Eliot Moss
2020-12-21 21:06 ` Achim Gratz
2020-12-21 20:47 ` Gary Johnson
2020-12-21 21:01 ` Fergus Daly
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=36027e5f-1240-8660-28c3-7e2aa855c2c8@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=cygwin@cygwin.com \
--cc=fergusd84@outlook.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).