Trial for 5.0.7

Trial for 5.0.7

[Peter Stephenson]

I'm going to release zsh 5.0.7 shortly and I've uploaded a trial
version, 5.0.6-dev-1. to http://www.zsh.org/pub/development/ if anyone
happens to get a chance to give it a quick once over.

Thanks
pws

Re: Trial for 5.0.7

[Ray Andrews]

On 10/02/2014 12:40 PM, Peter Stephenson wrote:
> I'm going to release zsh 5.0.7 shortly and I've uploaded a trial
> version, 5.0.6-dev-1. to http://www.zsh.org/pub/development/ if anyone
> happens to get a chance to give it a quick once over.
>
> Thanks
> pws
>
Is there some simple way to try that and keep the trusty version on hand 
as well? If I did run into some glitch it would be nice to be able to 
restart a shell with the known version, and flip back and forth quickly 
so as to verify what was going on.

Re: Trial for 5.0.7

[Bart Schaefer]

On Oct 4,  7:08am, Ray Andrews wrote:
}
} Is there some simple way to try that and keep the trusty version on hand 
} as well?

The simplest way I can think of involves a little preparation:

1. Copy all your ~/.z* config files to a new directory, let's call it
   ~/.zsh-trial

2. Edit ~/.zsh-trial/.zshenv to add

   fpath=(/path/to/your/zsh/sources/Completion**/*(/) $fpath)

3. When building zsh, "configure --disable-dynamic ..." so that you don't
   have to worry about mucking with module_path, which is a bit horrific

4. I've appended the contents of an edited config.modules below; replace
   your config.modules with it before running "make" so that you link in
   all the testable modules.  (It's not an attachment because the list
   archive prefers it that way.)

5. Do not "make install"; instead run the trial from the build tree as

	ZDOTDIR=$HOME/.zsh-trial Src/zsh


Here's the config.modules edit.  I keep it around as config.modules.local
because it has to be re-copied onto config.modules after any re-configure.

# -- 8< -- config.modules.local -- 8< ---
name=zsh/main modfile=Src/zsh.mdd link=static auto=yes load=yes functions=Functions/Chpwd/* Functions/Exceptions/* Functions/Misc/* Functions/MIME/* Functions/Prompts/* Functions/VCS_Info/* Functions/VCS_Info/Backends/*
name=zsh/rlimits modfile=Src/Builtins/rlimits.mdd link=static auto=yes load=yes
name=zsh/sched modfile=Src/Builtins/sched.mdd link=static auto=yes load=yes
name=zsh/attr modfile=Src/Modules/attr.mdd link=no auto=yes load=no
name=zsh/cap modfile=Src/Modules/cap.mdd link=no auto=yes load=no
name=zsh/clone modfile=Src/Modules/clone.mdd link=no auto=yes load=no
name=zsh/curses modfile=Src/Modules/curses.mdd link=no auto=yes load=no
name=zsh/datetime modfile=Src/Modules/datetime.mdd link=static auto=yes load=no functions=Functions/Calendar/*
name=zsh/db/gdbm modfile=Src/Modules/db_gdbm.mdd link=no auto=yes load=no
name=zsh/example modfile=Src/Modules/example.mdd link=static auto=yes load=no
name=zsh/files modfile=Src/Modules/files.mdd link=no auto=yes load=no
name=zsh/langinfo modfile=Src/Modules/langinfo.mdd link=static auto=yes load=no
name=zsh/mapfile modfile=Src/Modules/mapfile.mdd link=no auto=yes load=no
name=zsh/mathfunc modfile=Src/Modules/mathfunc.mdd link=static auto=yes load=no
name=zsh/newuser modfile=Src/Modules/newuser.mdd link=no auto=yes load=no functions=Scripts/newuser Functions/Newuser/*
name=zsh/parameter modfile=Src/Modules/parameter.mdd link=static auto=yes load=yes
name=zsh/pcre modfile=Src/Modules/pcre.mdd link=static auto=yes load=no
name=zsh/regex modfile=Src/Modules/regex.mdd link=static auto=yes load=no
name=zsh/net/socket modfile=Src/Modules/socket.mdd link=no auto=yes load=no
name=zsh/stat modfile=Src/Modules/stat.mdd link=no auto=yes load=no
name=zsh/system modfile=Src/Modules/system.mdd link=static auto=yes load=no
name=zsh/net/tcp modfile=Src/Modules/tcp.mdd link=no auto=yes load=no functions=Functions/TCP/*
name=zsh/termcap modfile=Src/Modules/termcap.mdd link=static auto=yes load=yes
name=zsh/terminfo modfile=Src/Modules/terminfo.mdd link=static auto=yes load=yes
name=zsh/zftp modfile=Src/Modules/zftp.mdd link=no auto=yes load=no functions=Functions/Zftp/*
name=zsh/zprof modfile=Src/Modules/zprof.mdd link=no auto=yes load=no
name=zsh/zpty modfile=Src/Modules/zpty.mdd link=static auto=yes load=no
name=zsh/zselect modfile=Src/Modules/zselect.mdd link=no auto=yes load=no
name=zsh/zutil modfile=Src/Modules/zutil.mdd link=static auto=yes load=yes
name=zsh/compctl modfile=Src/Zle/compctl.mdd link=static auto=yes load=yes
name=zsh/complete modfile=Src/Zle/complete.mdd link=static auto=yes load=yes functions=Completion/*comp* Completion/AIX/*/* Completion/BSD/*/* Completion/Base/*/* Completion/Cygwin/*/* Completion/Darwin/*/* Completion/Debian/*/* Completion/Linux/*/* Completion/Mandriva/*/* Completion/Redhat/*/* Completion/Solaris/*/* Completion/openSUSE/*/* Completion/Unix/*/* Completion/X/*/* Completion/Zsh/*/*
name=zsh/complist modfile=Src/Zle/complist.mdd link=static auto=yes load=yes
name=zsh/computil modfile=Src/Zle/computil.mdd link=static auto=yes load=yes
name=zsh/deltochar modfile=Src/Zle/deltochar.mdd link=no auto=yes load=no
name=zsh/zle modfile=Src/Zle/zle.mdd link=static auto=yes load=yes functions=Functions/Zle/*
name=zsh/zleparameter modfile=Src/Zle/zleparameter.mdd link=static auto=yes load=yes
# -- 8< -- config.modules.local -- 8< ---

Re: Trial for 5.0.7

[Ray Andrews]

On 10/04/2014 08:46 AM, Bart Schaefer wrote:
> On Oct 4,  7:08am, Ray Andrews wrote:
> }
> } Is there some simple way to try that and keep the trusty version on hand
> } as well?
>
> The simplest way I can think of involves a little preparation:
Thanks Bart, I'll give it a go.

Re: Trial for 5.0.7

[Ray Andrews]

Gentlemen,

Trying bravely to build (I've never done nuthin' like this before):

I get this far:

pts/2 HP-y11-5-Debian3 root /aMisc/Zshbuild/zsh-5.0.6-dev-1 $ make 
install.modules
make[1]: Entering directory '/aMisc/Zshbuild/zsh-5.0.6-dev-1/Src'
cd .. && /bin/sh $top_srcdir/Src/mkmakemod.sh Src Makemod
creating Src/Makemod.in
config.status: creating Src/Makemod
make[2]: Entering directory '/aMisc/Zshbuild/zsh-5.0.6-dev-1/Src'
make[3]: Entering directory '/aMisc/Zshbuild/zsh-5.0.6-dev-1/Src/Builtins'
make[3]: *** No rule to make target 'install.modules'.  Stop.
make[3]: Leaving directory '/aMisc/Zshbuild/zsh-5.0.6-dev-1/Src/Builtins'
Makemod:374: recipe for target 'install.modules' failed
make[2]: *** [install.modules] Error 1
make[2]: Leaving directory '/aMisc/Zshbuild/zsh-5.0.6-dev-1/Src'
Makefile:452: recipe for target 'install.modules' failed
make[1]: *** [install.modules] Error 2
make[1]: Leaving directory '/aMisc/Zshbuild/zsh-5.0.6-dev-1/Src'
Makefile:220: recipe for target 'install.modules' failed
make: *** [install.modules] Error 2

In 'Makefile' 'prefix = /usr/local'  so that seems ok.

List of directories in /usr/local:

pts/0 HP-y11-5-Debian3 root /usr/local $ l ,d

Sorting Directories Backwards by Name ():

drwxrwsr-x 2 4.0K 2014-02-09//17:50:42 src/
drwxrwsr-x 9 4.0K 2014-08-26//08:06:02 share/
drwxrwsr-x 2 4.0K 2014-02-09//17:50:42 sbin/
drwxrwsr-x 4 4.0K 2014-10-06//19:09:49 lib/
drwxrwsr-x 2 4.0K 2014-02-09//17:50:42 include/
drwxrwsr-x 2 4.0K 2014-02-09//17:50:42 games/
drwxrwsr-x 2 4.0K 2014-02-09//17:50:42 etc/
drwxrwsr-x 2 4.0K 2014-09-26//18:27:52 bin/
lrwxrwxrwx 1    9 2014-02-09//17:50:42 man -> share/man/

So I have no idea what might be wrong.
Does it matter that my build directory '/aMisc' is on another partition?

'./configure' seemed happy enough.

Re: Trial for 5.0.7

[Bart Schaefer]

On Wed, Oct 8, 2014 at 1:06 PM, Ray Andrews <rayandrews@eastlink.ca> wrote:
> Gentlemen,
>
> Trying bravely to build (I've never done nuthin' like this before):
>
> I get this far:
>
> pts/2 HP-y11-5-Debian3 root /aMisc/Zshbuild/zsh-5.0.6-dev-1 $ make
> install.modules

The various "install" targets assume that you've done a "make all"
first, i.e., there are implicit dependencies that are not explicit in
the makefiles constructed by configure, so you can't just dive
directly into installing.

In particular "make all" builds the set of additional makefiles that
know how to "make install.modules".

combine/merge .history?

[Ray Andrews]

Hi,

Can we do simple cut/copy/paste operations in the .histfile?  Reason is 
that I have a bunch of command lines in an old .histfile that I'd love 
to import into the working copy.  I'm a bit afraid to try tho because 
the 'lead numbers' are so different:

1390861257:0;mcedit lilo.conf
1390861320:0;lilo -C /boot/lilo.conf
1390861514:0;startxfce4
1390861527:0;modprobe nouveau

  1074* c Boot
  1075* e zshrc
  1076* A
  1077* man pv

... and I'm afraid I might discombobulate something.

Re: combine/merge .history?

[Bart Schaefer]

On Oct 13, 10:03am, Ray Andrews wrote:
}
} Can we do simple cut/copy/paste operations in the .histfile?

If you're using the EXTENDED_HISTORY option or features that rely on
that format like shared/incremental history -- which it appears from
your excerpt that you are -- then it's not entirely safe to edit the
history by hand.

I don't know of anything particular that will go wrong, especially if
you only change it while no shells are running to access it, but you
should not be surprised if the history state gets a little odd.

However, you have a somewhat different case here:  You have history
files in two different formats that you want to combine.  To do this
you'll have to be careful to edit all entries into a single format.

} the 'lead numbers' are so different:

In the first example ...

} 1390861257:0;mcedit lilo.conf
} 1390861320:0;lilo -C /boot/lilo.conf
} 1390861514:0;startxfce4
} 1390861527:0;modprobe nouveau

... those are timestamps [e.g. 1390861527 is Mon Jan 27 14:25:27 2014
(PST)] followed by durations in seconds that the command took to run
(which always record as zero when sharing history, see the new option
INC_APPEND_HISTORY_TIME).

This example ...

}   1074* c Boot
}   1075* e zshrc
}   1076* A
}   1077* man pv

... doesn't look like anything zsh ever saved; those would appear to
just be line numbers.  When not using EXTENDED_HISTORY et al., zsh
saves the commands without any leading prefix.

Your best bet is probably to remove everything up to the first ";"
from each line of the file with the timestamps, remove everything
through "* " from each line of the other, then combine the two and
try to read them into a "zsh -f" with "fc -R" (set HISTSIZE large
enough first).  If that works as you wanted, repeat the "fc -R" in
a regular login shell and save with "fc -A".

Re: combine/merge .history?

[Ray Andrews]

On 10/13/2014 10:59 AM, Bart Schaefer wrote:

Bart:

> This example ...
>
> }   1074* c Boot
> }   1075* e zshrc
> }   1076* A
> }   1077* man pv
>
> ... doesn't look like anything zsh ever saved; those would appear to
> just be line numbers.  When not using EXTENDED_HISTORY et al., zsh
> saves the commands without any leading prefix.
>
But:

pts/2 HP-y5--5-Debian1 root / $ history
  1086* W
  1087* l ,m
  1088* hdparm -C /dev/sda
  1089* cat .histfile
  1091  i history
  1092  c
  1093  g ,r "gedit /aWorking"
  1095* l launcher-25
  1096* l launcher-29
  1098* cat launcher-25/13913154231.desktop
  1099* cat launcher-29/13313195471.desktop
  1100* cat launcher-29/13916352102.desktop
  1101  meld launcher-25/13913154231.desktop launcher-29/13916352102.desktop
  1102* c .
  1103* xfce4-panel --add=launcher 
/root/.config/xfce4/panel/launcher-25/13913154231.desktop
  1105  /

... so that seems to be plain vanilla history output, no? 
EXTENDEDHISTORY is being used (I think,  I hope).

Re: combine/merge .history?

[Bart Schaefer]

On Oct 13,  1:33pm, Ray Andrews wrote:
} Subject: Re: combine/merge .history?
}
} On 10/13/2014 10:59 AM, Bart Schaefer wrote:
} 
} Bart:
} 
} > }   1074* c Boot
} > }   1075* e zshrc
} > }   1076* A
} > }   1077* man pv
} >
} > ... doesn't look like anything zsh ever saved
} 
} pts/2 HP-y5--5-Debian1 root / $ history
}   1086* W
}   1087* l ,m
}   1088* hdparm -C /dev/sda
}   1089* cat .histfile
} 
} ... so that seems to be plain vanilla history output, no? 

Sorry, I thought you were giving examples of file contents, not examples
of the output of the "history" command.  I didn't recognize it because I
never use SHARE_HISTORY and forgot that "foreign" history entries get
marked with a "*".

So ... if the format of entries *in the two files* looks similar, you
should be OK to combine them.  If both of them have the extended format
(timestamp:elapsed;command) then you should be able to merge them and
sort the result by timestamp without any major problems.

Just beware of multi-line entries, e.g., a plain "sort -n" will garble
those badly.

Re: combine/merge .history?

[Ray Andrews]

On 10/13/2014 02:33 PM, Bart Schaefer wrote:
> Sorry, I thought you were giving examples of file contents, not examples
> of the output of the "history" command.  I didn't recognize it because I
> never use SHARE_HISTORY and forgot that "foreign" history entries get
> marked with a "*".
My mistake Bart, I should have used the same method for showing both. 
Now that I 'cat' both
the new and old .histfiles, they format exactly the same.
> So ... if the format of entries *in the two files* looks similar, you
> should be OK to combine them.  If both of them have the extended format
> (timestamp:elapsed;command) then you should be able to merge them and
> sort the result by timestamp without any major problems.
>
> Just beware of multi-line entries, e.g., a plain "sort -n" will garble
> those badly.
OK, I"m good to go.