You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(2) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(3) |
Feb
(1) |
Mar
(2) |
Apr
(22) |
May
(52) |
Jun
(43) |
Jul
(36) |
Aug
(59) |
Sep
(37) |
Oct
(55) |
Nov
(39) |
Dec
(36) |
| 2005 |
Jan
(64) |
Feb
(40) |
Mar
(62) |
Apr
(58) |
May
(256) |
Jun
(77) |
Jul
(80) |
Aug
(39) |
Sep
(56) |
Oct
(36) |
Nov
(113) |
Dec
(68) |
| 2006 |
Jan
(43) |
Feb
(64) |
Mar
(69) |
Apr
(60) |
May
(71) |
Jun
(53) |
Jul
(63) |
Aug
(63) |
Sep
(76) |
Oct
(85) |
Nov
(82) |
Dec
(73) |
| 2007 |
Jan
(75) |
Feb
(82) |
Mar
(84) |
Apr
(104) |
May
(67) |
Jun
(101) |
Jul
(107) |
Aug
(138) |
Sep
(128) |
Oct
(106) |
Nov
(112) |
Dec
(112) |
| 2008 |
Jan
(94) |
Feb
(87) |
Mar
(146) |
Apr
(169) |
May
(75) |
Jun
(26) |
Jul
(26) |
Aug
(7) |
Sep
(18) |
Oct
(53) |
Nov
(42) |
Dec
(19) |
| 2009 |
Jan
(43) |
Feb
(39) |
Mar
(18) |
Apr
(45) |
May
(66) |
Jun
(87) |
Jul
(56) |
Aug
(41) |
Sep
(56) |
Oct
(139) |
Nov
(98) |
Dec
(88) |
| 2010 |
Jan
(81) |
Feb
(79) |
Mar
(83) |
Apr
(97) |
May
(124) |
Jun
(84) |
Jul
(53) |
Aug
(85) |
Sep
(89) |
Oct
(50) |
Nov
(98) |
Dec
(78) |
| 2011 |
Jan
(97) |
Feb
(74) |
Mar
(68) |
Apr
(54) |
May
(63) |
Jun
(59) |
Jul
(65) |
Aug
(58) |
Sep
(37) |
Oct
(40) |
Nov
(59) |
Dec
(35) |
| 2012 |
Jan
(16) |
Feb
(56) |
Mar
(63) |
Apr
(25) |
May
(48) |
Jun
(58) |
Jul
(20) |
Aug
(13) |
Sep
(43) |
Oct
(35) |
Nov
(20) |
Dec
(17) |
| 2013 |
Jan
(22) |
Feb
(11) |
Mar
(51) |
Apr
(34) |
May
(57) |
Jun
(27) |
Jul
(70) |
Aug
(30) |
Sep
(38) |
Oct
(53) |
Nov
(40) |
Dec
(25) |
| 2014 |
Jan
(26) |
Feb
(35) |
Mar
(60) |
Apr
(12) |
May
(17) |
Jun
(15) |
Jul
(9) |
Aug
(18) |
Sep
(46) |
Oct
(18) |
Nov
(19) |
Dec
(15) |
| 2015 |
Jan
(17) |
Feb
(28) |
Mar
(21) |
Apr
(54) |
May
(36) |
Jun
(8) |
Jul
(30) |
Aug
(13) |
Sep
(3) |
Oct
(28) |
Nov
(3) |
Dec
(3) |
| 2016 |
Jan
(11) |
Feb
(9) |
Mar
(29) |
Apr
(10) |
May
(8) |
Jun
(5) |
Jul
(50) |
Aug
(57) |
Sep
(13) |
Oct
(5) |
Nov
(17) |
Dec
(11) |
| 2017 |
Jan
(3) |
Feb
(23) |
Mar
(16) |
Apr
(7) |
May
(15) |
Jun
(12) |
Jul
(48) |
Aug
(15) |
Sep
(3) |
Oct
(20) |
Nov
(28) |
Dec
(21) |
| 2018 |
Jan
(13) |
Feb
(21) |
Mar
(21) |
Apr
(7) |
May
(3) |
Jun
(7) |
Jul
(27) |
Aug
(38) |
Sep
(4) |
Oct
(30) |
Nov
(22) |
Dec
|
| 2019 |
Jan
(5) |
Feb
(16) |
Mar
(1) |
Apr
(9) |
May
(7) |
Jun
(20) |
Jul
(13) |
Aug
(3) |
Sep
(2) |
Oct
(2) |
Nov
(2) |
Dec
(4) |
| 2020 |
Jan
(6) |
Feb
(11) |
Mar
(1) |
Apr
(18) |
May
(4) |
Jun
(5) |
Jul
(12) |
Aug
(1) |
Sep
(3) |
Oct
(7) |
Nov
(1) |
Dec
(17) |
| 2021 |
Jan
(1) |
Feb
(11) |
Mar
(16) |
Apr
(6) |
May
(5) |
Jun
(1) |
Jul
(1) |
Aug
(2) |
Sep
(8) |
Oct
(10) |
Nov
(4) |
Dec
(4) |
| 2022 |
Jan
(9) |
Feb
(35) |
Mar
(4) |
Apr
|
May
(3) |
Jun
(49) |
Jul
(11) |
Aug
|
Sep
(5) |
Oct
(2) |
Nov
(16) |
Dec
(13) |
| 2023 |
Jan
|
Feb
(8) |
Mar
(3) |
Apr
|
May
(8) |
Jun
|
Jul
(5) |
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
(2) |
| 2024 |
Jan
(6) |
Feb
(9) |
Mar
|
Apr
(26) |
May
(24) |
Jun
|
Jul
(4) |
Aug
(2) |
Sep
(1) |
Oct
(10) |
Nov
(9) |
Dec
|
| 2025 |
Jan
|
Feb
(22) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
(4) |
| 2026 |
Jan
|
Feb
(24) |
Mar
(20) |
Apr
(18) |
May
(2) |
Jun
(2) |
Jul
(2) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Mátyás S. <ser...@gm...> - 2014-03-13 21:53:20
|
Hi all, I have a problem with setting the title for a diagram made with gnuplot. I would like to import the first line of the datafile as a string, and write it above the diagram, as a title. Then the numerical data can be plotted. How can I do it? Could you please help me? I attached a sample datafile for illustration. Thanks, Mat |
|
From: Rhys U. <rhy...@gm...> - 2014-03-13 16:24:23
|
> Apart from the question of whether a new or modified variant of
> "set key autotitle" is warranted, I suggest that for plotting
> 30 files with column 'x' an appropriate set of commands is
>
> LIST = "file1 file2 file3 .... file30"
> plot for [NAME in LIST] NAME.".dat" using 0:"x" title NAME
Understood.
That recipe still runs afoul of the
LIST = "file1 file2 file3 .... file30"
plot for [NAME in LIST] NAME.".dat" using 0:"x" title NAME.' using 0:"x"'
issue, especially with computed column names, that I mentioned in my
response to Hans.
I really do want to label with the entire {"<datafile>"
{datafile-modifiers}}} handed to the plot command.
Thanks for everyone's time,
Rhys
|
|
From: Rhys U. <rhy...@gm...> - 2014-03-13 16:15:03
|
>> plot 'foo.dat' using 0:"x", 'bar.dat' using 0:"x"
> So bite the bullet and _tell_ it what title you want.
plot 'foo' using 0:'x' title "'foo' using 0:'x'", \
'bar' using 0:'x' title "'bar' using 0:'x'"
Bleeeech. Now, consider the possibility of complicated computed columns...
> There's always a limit to the possible success of tools trying to read people's mind. If they fail, just tell them what to do.
Agreed. But before jumping through the hoops in the foo/bar with
title example just above, I'd much prefer to turn off the tools'
mindreading tendencies. Hence my original note.
- Rhys
|
|
From: Ethan A M. <eam...@gm...> - 2014-03-13 15:17:32
|
On Wednesday, 12 March 2014 11:05:50 PM Rhys Ulerich wrote: > Hi Ethan, > > Thanks for taking a look and the time to respond. > > > Because in the 4th plots you tell it to read the columnheader > > (in order to find column "x") and so the input data must necessarily > > _have_ columnheaders. That is the same thing that > > you are telling it with "set key autotitle columnheader". > > Same request - same result. > > > > Therefore plot #4 shows the intended behaviour. > > I have a use case where that behavior becomes a decided usability hiccup. > > set key autotitle > plot 'foo.dat' using 0:"x", 'bar.dat' using 0:"x" > > Now I have two autotitled legend entries that uselessly both say "x". > I can't tell them apart. The file name is the only distinguishing > feature and using "x" suppresses the filenames' appearance. I > implicitly didn't ask for column headers because I omitted > "columnheader" when turning on autotitling. I can't turn this > behavior off because there's no "set key autotitle nocolumnheader". > > The usability hiccup becomes worse as the number of files involved and > number of columns increase. I'm somewhere in the 30+ files and 200+ > column range on a daily basis. > - Rhys Apart from the question of whether a new or modified variant of "set key autotitle" is warranted, I suggest that for plotting 30 files with column 'x' an appropriate set of commands is LIST = "file1 file2 file3 .... file30" plot for [NAME in LIST] NAME.".dat" using 0:"x" title NAME Ethan |
|
From: Michael S. <mic...@me...> - 2014-03-13 14:25:06
|
Hello, is there a way to fill the space below a "histeps" curve like the style "fillsteps" does it for a "steps"-like curve? Best regards, Michael |
|
From: Hans-Bernhard B. <HBB...@t-...> - 2014-03-13 11:58:39
|
On 13.03.2014 05:05, Rhys Ulerich wrote: > I have a use case where that behavior becomes a decided usability hiccup. > > set key autotitle > plot 'foo.dat' using 0:"x", 'bar.dat' using 0:"x" > > Now I have two autotitled legend entries that uselessly both say "x". > I can't tell them apart. So bite the bullet and _tell_ it what title you want. There's always a limit to the possible success of tools trying to read people's mind. If they fail, just tell them what to do. |
|
From: Rhys U. <rhy...@gm...> - 2014-03-13 04:06:18
|
Hi Ethan,
Thanks for taking a look and the time to respond.
> Because in the 4th plots you tell it to read the columnheader
> (in order to find column "x") and so the input data must necessarily
> _have_ columnheaders. That is the same thing that
> you are telling it with "set key autotitle columnheader".
> Same request - same result.
>
> Therefore plot #4 shows the intended behaviour.
I have a use case where that behavior becomes a decided usability hiccup.
set key autotitle
plot 'foo.dat' using 0:"x", 'bar.dat' using 0:"x"
Now I have two autotitled legend entries that uselessly both say "x".
I can't tell them apart. The file name is the only distinguishing
feature and using "x" suppresses the filenames' appearance. I
implicitly didn't ask for column headers because I omitted
"columnheader" when turning on autotitling. I can't turn this
behavior off because there's no "set key autotitle nocolumnheader".
The usability hiccup becomes worse as the number of files involved and
number of columns increase. I'm somewhere in the 30+ files and 200+
column range on a daily basis.
> If your column header were "3rd_base" or something
> like that, plot commands #1 would produce an incorrect plot
> with a spurious initial data point at 3.
I personally make my column headers to be valid C identifiers (so
"third_base" not "3rd_base") deliberately so that skipping the first
invalid line is makes "using 0:1" perfectly well-behaved.
> Plot #2 is arguably a demonstration that we should have two
> distinct commands that don't really exist yet:
> set noautotitle columnheader
> set autotitle nocolumnheader
How about just the current three with the middle one amended to fix
the usability hiccup I described?
set key noautotitle: no autotitles, period
set key autotitle: autotitles from plot specifier without magical
columnheader behavior that wasn't requested
set key autotitle columnheader: autotitles with magical columnheaders
Otherwise you'll have to explain that
set key noautotitle nocolumnheader
doesn't really mean
set key autotitle columnheader
on account of the double negative.
All that said, hell of a tool. Thank you for the effort you put into it.
- Rhys
|
|
From: Ethan A M. <eam...@gm...> - 2014-03-13 01:49:43
|
On Wednesday, 12 March 2014 01:21:36 PM Rhys Ulerich wrote: > Why does the first plot below obey "set key noautotitle" while the > second one ignores it? > > $ gnuplot -V > gnuplot 4.6 patchlevel 5 > > $ file ~/.gnuplot # No rcfile magic up my sleeve > /h2/rhys/.gnuplot: cannot open `/h2/rhys/.gnuplot' (No such file or directory) > > $ cat data > x > 1 > 2 > 3 > > $ gnuplot > gnuplot> set key noautotitle > gnuplot> plot 'data' using 0:1 # First > gnuplot> plot 'data' using 0:"x" # Second > gnuplot> set key autotitle > gnuplot> plot 'data' using 0:1 # Third > gnuplot> plot 'data' using 0:"x" # Fourth > > Why does this third plot autotitle "correctly" from the plot > specification while the fourth behaves as if I said "set key autotitle > columnheader"? Because in the 4th plots you tell it to read the columnheader (in order to find column "x") and so the input data must necessarily _have_ columnheaders. That is the same thing that you are telling it with "set key autotitle columnheader". Same request - same result. Therefore plot #4 shows the intended behaviour. Plot #2 - maybe not. On the other hand, plot command #1 is just wrong. You luck out because the column header happens to be a string that cannot be parsed as valid numeric input, so the first line is treated as containing an undefined/missing data value. If your column header were "3rd_base" or something like that, plot commands #1 would produce an incorrect plot with a spurious initial data point at 3. > I find the behaviors on the second and fourth plots to be buggy, but > perhaps I'm misunderstanding something implicit about using a named > column. > - Rhys I don't see anything remotely buggy about #3 or #4. Plots #1 should probably print a warning. Plot #2 is arguably a demonstration that we should have two distinct commands that don't really exist yet: set noautotitle columnheader set autotitle nocolumnheader Ethan |
|
From: Rhys U. <rhy...@gm...> - 2014-03-12 18:22:04
|
Why does the first plot below obey "set key noautotitle" while the second one ignores it? $ gnuplot -V gnuplot 4.6 patchlevel 5 $ file ~/.gnuplot # No rcfile magic up my sleeve /h2/rhys/.gnuplot: cannot open `/h2/rhys/.gnuplot' (No such file or directory) $ cat data x 1 2 3 $ gnuplot gnuplot> set key noautotitle gnuplot> plot 'data' using 0:1 # First gnuplot> plot 'data' using 0:"x" # Second Why does this third plot autotitle "correctly" from the plot specification while the fourth behaves as if I said "set key autotitle columnheader"? gnuplot> set key autotitle gnuplot> plot 'data' using 0:1 # Third gnuplot> plot 'data' using 0:"x" # Fourth I find the behaviors on the second and fourth plots to be buggy, but perhaps I'm misunderstanding something implicit about using a named column. - Rhys |
|
From: Natu <inc...@rj...> - 2014-03-11 01:19:38
|
On 03/10/2014 09:36 AM, Thomas Sefzick wrote: > Natu <incoming-sourceforge <at> rjl.com> writes: >> ... >> Here's the data in test4.dat >> >> 03/09/14,23:59:31,61.9 >> 03/09/14,00:09:31,66.5 >> ... > the day is wrong in the first data line, > it should be 03/08/14 > > > ------------------------------------------------------------------------------ > Learn Graph Databases - Download FREE O'Reilly Book > "Graph Databases" is the definitive new guide to graph databases and their > applications. Written by three acclaimed leaders in the field, > this first edition is now available. Download your free book today! > http://p.sf.net/sfu/13534_NeoTech > _______________________________________________ > gnuplot-info mailing list > gnu...@li... > Membership management via: https://lists.sourceforge.net/lists/listinfo/gnuplot-info Thank You for pointing that out. It was a bug in the program that generated the data. Problem solved. Nataraj |
|
From: Thomas S. <t.s...@fz...> - 2014-03-10 16:36:39
|
Natu <incoming-sourceforge <at> rjl.com> writes: > ... > Here's the data in test4.dat > > 03/09/14,23:59:31,61.9 > 03/09/14,00:09:31,66.5 > ... the day is wrong in the first data line, it should be 03/08/14 |
|
From: Natu <inc...@rj...> - 2014-03-10 15:54:09
|
On 03/10/2014 05:05 AM, Hans-Bernhard Bröker wrote:
> On 10.03.2014 01:03, Natu wrote:
>
>> set multiplot
>> plot "GKLOG001_25452.AVG" using 1:7 with linespoints title "\n5
>> minute min/avg/max" lt rgb "blue";
>> plot "GKLOG001_25452.MIN" using 1:7 with linespoints title "" lt
>> rgb
>> "green";
>> plot "GKLOG001_25452.MAX" using 1:7 with linespoints title "" lt
>> rgb
>> "red";
>
> This use of 'multiplot' is ill-advised. It will not have any positive
> effect compared to a more straight-forward
>
> plot "GKLOG001_25452.AVG" u 1:7 w lp t "avg" lt rgb "blue", \
> "GKLOG001_25452.MIN" u 1:7 w lp t"min" lt rgb "green", \
> "GKLOG001_25452.MAX" u 1:7 wlp t "max" lt rgb "red"
>
>> When I plot certain data files, gnuplot draws a line across the graph
>> showing the increasing/decreasing trend of the data.
>
> I'm reasonably sure this has nothing to do with any trend. But it's
> hard to know what else it might be, because you don't show any data
> that triggered it.
>
Thank you for all the replies. Most seemed to think that it was related
to the multiplot. I have created a very simple example with no
multiplot. Here are the commands and data that produced this. I am
running gnuplot 4.4 patchlevel 3 under ubuntu 12.04. Same problem under
gnuplot 4.2. I was a little unsure about parsing the date/time from two
columns, but I got that from several web page examples. It seems to
work correctly.
set datafile separator ","
set xdata time
set timefmt "%m/%d/%y,%H:%M:%S"
set format x "%H:%M\n%m/%d"
plot "test4.dat" using 1:3 with linespoints;
Here's the data in test4.dat
03/09/14,23:59:31,61.9
03/09/14,00:09:31,66.5
03/09/14,00:19:31,65.1
03/09/14,00:29:31,66.4
03/09/14,00:39:31,67.6
03/09/14,00:49:31,63.1
03/09/14,00:59:31,62.4
03/09/14,01:09:31,61.3
03/09/14,01:19:31,61.2
03/09/14,01:29:31,68.8
03/09/14,01:39:31,59.8
03/09/14,01:49:31,65.5
03/09/14,01:59:31,61.5
03/09/14,02:09:31,67.2
03/09/14,02:19:31,63.9
03/09/14,02:29:31,65.1
03/09/14,02:39:31,60.3
03/09/14,02:49:31,64.2
03/09/14,02:59:31,59.7
03/09/14,03:09:31,59.1
03/09/14,03:19:31,61
03/09/14,03:29:31,66
03/09/14,03:39:31,63.9
03/09/14,03:49:31,60.2
03/09/14,03:59:31,61.3
03/09/14,04:09:31,63.2
03/09/14,04:19:31,64.9
03/09/14,04:29:31,66
03/09/14,04:39:31,60.5
03/09/14,04:49:31,66.3
03/09/14,04:59:31,62.3
03/09/14,05:09:31,62.3
03/09/14,05:19:31,65.2
03/09/14,05:29:31,63.5
03/09/14,05:39:31,65.2
03/09/14,05:49:31,60.8
03/09/14,05:59:31,62.1
03/09/14,06:09:31,66.6
03/09/14,06:19:31,67.9
03/09/14,06:29:31,64
03/09/14,06:39:31,62.3
03/09/14,06:49:31,62.6
03/09/14,06:59:31,62.5
03/09/14,07:09:31,61.8
03/09/14,07:19:31,60.9
03/09/14,07:29:31,62.7
03/09/14,07:39:31,59.9
03/09/14,07:49:31,59.1
03/09/14,07:59:31,62.6
03/09/14,08:09:31,65.3
03/09/14,08:19:31,58.2
03/09/14,08:29:31,60.8
Thank You,
Natu
|
|
From: ckm <c_...@ya...> - 2014-03-10 14:07:56
|
I want to do curve fitting with complex number. I just wanted to know if it is possible because gnuplot takes complex number in many functions. -- View this message in context: http://gnuplot.10905.n7.nabble.com/Complex-number-tp18211.html Sent from the Gnuplot - User mailing list archive at Nabble.com. |
|
From: Hans-Bernhard B. <HBB...@t-...> - 2014-03-10 12:05:42
|
On 10.03.2014 01:03, Natu wrote:
> set multiplot
> plot "GKLOG001_25452.AVG" using 1:7 with linespoints title "\n5
> minute min/avg/max" lt rgb "blue";
> plot "GKLOG001_25452.MIN" using 1:7 with linespoints title "" lt rgb
> "green";
> plot "GKLOG001_25452.MAX" using 1:7 with linespoints title "" lt rgb
> "red";
This use of 'multiplot' is ill-advised. It will not have any positive
effect compared to a more straight-forward
plot "GKLOG001_25452.AVG" u 1:7 w lp t "avg" lt rgb "blue", \
"GKLOG001_25452.MIN" u 1:7 w lp t"min" lt rgb "green", \
"GKLOG001_25452.MAX" u 1:7 wlp t "max" lt rgb "red"
> When I plot certain data files, gnuplot draws a line across the graph
> showing the increasing/decreasing trend of the data.
I'm reasonably sure this has nothing to do with any trend. But it's
hard to know what else it might be, because you don't show any data that
triggered it.
|
|
From: Natu <inc...@rj...> - 2014-03-10 00:35:51
|
I have a bunch of datafiles that I am plotting as follows:
set datafile separator ","
set xdata time
set xlabel "time/date"
set grid
set timefmt "%m/%d/%y,%H:%M:%S"
set format x "%H:%M\n%m/%d"
set ylabel "counts"
set yrange ["42":"91"]
set multiplot
plot "GKLOG001_25452.AVG" using 1:7 with linespoints title "\n5
minute min/avg/max" lt rgb "blue";
plot "GKLOG001_25452.MIN" using 1:7 with linespoints title "" lt rgb
"green";
plot "GKLOG001_25452.MAX" using 1:7 with linespoints title "" lt rgb
"red";
When I plot certain data files, gnuplot draws a line across the graph
showing the increasing/decreasing trend of the data. With other data
the line does not get drawn. I am calling this a trendline because I
don't know what else it would be called (Maybe a fit line?). I have not
given any commands asking it to do this.
Does anyone know what this is and how it might be turned off?
Thank You,
Natu
|
|
From: Rhys U. <rhy...@gm...> - 2014-03-09 18:00:11
|
> Please file a bug report on the SourceForge tracker so > we don't lose track of it Filed as https://sourceforge.net/p/gnuplot/bugs/1348/. Thanks, Rhys |
|
From: sfeam <eam...@gm...> - 2014-03-09 17:52:16
|
On Sunday, 09 March 2014 12:07:00 PM Rhys Ulerich wrote: > Just confirmed that the recreate > > > $gnuplot > > gnuplot> set term x11 persist > > gnuplot> set termoption enhanced > > gnuplot> plot sin(x) > > gnuplot> exit > > misbehaves on 4.6.5 too. > > - Rhys Please file a bug report on the SourceForge tracker so we don't lose track of it. Patches and commentary are currently coming in torrents due to discussion about what should be changed, fixed, or added for version 5. I'm afraid your note here will get lost in the flood. Ethan |
|
From: Rhys U. <rhy...@gm...> - 2014-03-09 17:07:27
|
Just confirmed that the recreate > $gnuplot > gnuplot> set term x11 persist > gnuplot> set termoption enhanced > gnuplot> plot sin(x) > gnuplot> exit misbehaves on 4.6.5 too. - Rhys |
|
From: Rhys U. <rhy...@gm...> - 2014-03-09 17:01:12
|
On 4.6.3 I see $gnuplot gnuplot> set term x11 persist gnuplot> plot sin(x) gnuplot> exit leave a persistent window as expected while $gnuplot gnuplot> set term x11 persist gnuplot> set termoption enhanced gnuplot> plot sin(x) gnuplot> exit does not. Curiously, $ gnuplot -persist gnuplot> set termoption enhanced gnuplot> set title 'Foo_0' gnuplot> plot sin(x) gnuplot> exit works and the title confirms that enhanced mode is working here. - Rhys |
|
From: Rhys U. <rhy...@gm...> - 2014-03-09 16:27:03
|
It feels weird that
save '|cat>>foo'
is required to append save command output to an existing file (on
4.6.3 at least).
- Rhys
|
|
From: Dima K. <gn...@di...> - 2014-03-06 19:04:15
|
Ethan Merritt <eam...@gm...> writes: > What about the files gnuplot-eldoc.el and gnuplot-eldoc.elc that are > generated from the master documentation file gnuplot.doc? Are they part > of gnuplot-mode or are they for something else entirely? Those aren't a part of gnuplot-mode. The .elc is a byte-compiled version of the .el. gnuplot-eldoc.el looks like it is meant to provide completion when creating gnuplot scripts, but it was never being installed in any meaningful way, so I've never used it (or heard of it for that matter). The newer gnuplot-mode tree provides this functionality in a different way. I'm pretty sure those files could be removed. They were undiscoverable, and are now handled in a more logical (and obvious) place. dima |
|
From: Ethan M. <eam...@gm...> - 2014-03-06 17:50:58
|
What about the files gnuplot-eldoc.el and gnuplot-eldoc.elc that are generated from the master documentation file gnuplot.doc? Are they part of gnuplot-mode or are they for something else entirely? On Thu, Mar 6, 2014 at 2:21 AM, Elias Assmann <eli...@gm...>wrote: > Hi Dima, > > On 03/05/2014 09:59 PM, Dima Kogan wrote: > > Hi Elias. The gnuplot emacs interface in the gnuplot distribution is out > > of date. A very updated mode is here: > > Way out of date actually! I did not really look at the header. > > And good catch, I have to say -- I did not say which source I was using. > > > https://github.com/bruceravel/gnuplot-mode > > > > You should patch that tree (if it doesn't have your fixes already). > > In fact, this already has > > (defun gnuplot-send-line-to-gnuplot () > … > (save-excursion > ;; go to start of continued command, or beginning of line > ;; if this is not a continuation of a previous line <JJO> > (gnuplot-beginning-of-continuation) > … > > For what it's worth, I agree that it would be better to remove the > outdated gnuplot.el from the gnuplot distribution :-). > > Thank you for pointing me to the new version. > > Elias > > > > ------------------------------------------------------------------------------ > Subversion Kills Productivity. Get off Subversion & Make the Move to > Perforce. > With Perforce, you get hassle-free workflows. Merge that actually works. > Faster operations. Version large binaries. Built-in WAN optimization and > the > freedom to use Git, Perforce or both. Make the move to Perforce. > > http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk > _______________________________________________ > gnuplot-info mailing list > gnu...@li... > Membership management via: > https://lists.sourceforge.net/lists/listinfo/gnuplot-info > |
|
From: Elias A. <eli...@gm...> - 2014-03-06 10:21:43
|
Hi Dima, On 03/05/2014 09:59 PM, Dima Kogan wrote: > Hi Elias. The gnuplot emacs interface in the gnuplot distribution is out > of date. A very updated mode is here: Way out of date actually! I did not really look at the header. And good catch, I have to say -- I did not say which source I was using. > https://github.com/bruceravel/gnuplot-mode > > You should patch that tree (if it doesn't have your fixes already). In fact, this already has (defun gnuplot-send-line-to-gnuplot () … (save-excursion ;; go to start of continued command, or beginning of line ;; if this is not a continuation of a previous line <JJO> (gnuplot-beginning-of-continuation) … For what it's worth, I agree that it would be better to remove the outdated gnuplot.el from the gnuplot distribution :-). Thank you for pointing me to the new version. Elias |
|
From: Dima K. <gn...@di...> - 2014-03-06 05:48:05
|
sfeam <sf...@us...> writes: > On Wednesday, 05 March 2014 12:59:17 PM Dima Kogan wrote: > >> Ethan and co: this came up last year, but we didn't do anything about >> it. Can we either remove the gnuplot emacs mode from the CVS tree (since >> it's maintained in github already), or make it obvious that the >> gnuplot.el hosted HERE is a mirror rather than the upstream? > > I would be happy to remove it. > But I didn't feel comfortable making that decision myself because > I am not an emacs user and have no feel for who would be > inconvenienced or otherwise unhappy if it disappears. > > Could you write up a short paragraph for the documentation, > the FAQ, and the README explaining what gnuplot-mode is, > who might want to use it, and where to find it? Hi Ethan. Here's a description that mostly comes from the source: ================================================================ The emacs gnuplot-mode is a major mode for composing gnuplot scripts and displaying their results using gnuplot. It can be obtained from MELPA or from a distribution such as Debian or Ubuntu. Otherwise, the source lives at https://github.com/bruceravel/gnuplot-mode This mode offers several tools to help you compose your scripts, including font-lock syntax colorization, a syntax table appropriate to gnuplot, key bindings, pull-down menus, indentation, keyword completions and variable customization using the Custom package. Once the script is composed, there are several function for sending some or all of the script to gnuplot. The interaction with the gnuplot process is within a comint buffer. Plots can optionally be displayed within Emacs. ================================================================ In non-emacs-speak, it provides facilities to make writing and running scripts easier. I really do think it should be removed. Not only does emacs have standardized packaging infrastructure that has this package in it, distros such as Debian carry it too. It's a bit of a historical accident that this ever lived in the gnuplot tree, but there's no reason for it at all anymore. If we have a list somewhere of frontends and libraries that use gnuplot, we should mention it there. dima |
|
From: Ethan A M. <eam...@gm...> - 2014-03-06 05:05:38
|
On Wednesday, 05 March 2014 12:59:17 PM Dima Kogan wrote: > Hi Elias. The gnuplot emacs interface in the gnuplot distribution is out > of date. A very updated mode is here: > > https://github.com/bruceravel/gnuplot-mode > > You should patch that tree (if it doesn't have your fixes already). > > Ethan and co: this came up last year, but we didn't do anything about > it. Can we either remove the gnuplot emacs mode from the CVS tree (since > it's maintained in github already), or make it obvious that the > gnuplot.el hosted HERE is a mirror rather than the upstream? > dima I would be happy to remove it. But I didn't feel comfortable making that decision myself because I am not an emacs user and have no feel for who would be inconvenienced or otherwise unhappy if it disappears. Could you write up a short paragraph for the documentation, the FAQ, and the README explaining what gnuplot-mode is, who might want to use it, and where to find it? thanks, Ethan > Elias Assmann <eli...@gm...> writes: > > > Hi, > > > > In gnuplot-mode, ‘gnuplot-send-line-to-gnuplot’ (C-c C-l) helpfully > > searches forward to the end of a continued line. However, I thought it > > would be even more helpful to also search backward to the beginning of > > the logical line. > > > > So below, you will find a version of the function that does that. > > > > HTH, > > > > Elias > > > > > > PS: My knowledge of Emacs Lisp is very incomplete … > > > > PPS: gnuplot-mode redefines C-m to newline-and-indent. This makes it > > awkward to get a newline without any indention. In my experience, most > > Emacs modes use C-j for “smart newline” (whatever that may mean in the > > mode's context) but leave C-m to mean plain newline. > |