Bug#614360: dos2unix doesn't work on windows 2003/2008 shares with debian 6.x
Hi Dirk, Thanks for the feedback. On Debian 6 some pointer is going out of range. On Debian 5 the same version of dos2unix works correctly. I conclude there is some difference in the system that triggers the problem. Could it be that your Debian 5 system is 64 bit and your Debian 6 system 32 bit? What is the output of 'gcc -v' on both systems? I searched on the internet and found that defining _FILE_OFFSET_BITS=64 could solve the problem. On Debian 6, could you open the Makefile, and change the line with CFLAGS = -O2 -Wall -D_LARGEFILE_SOURCE $(RPM_OPT_FLAGS) to CFLAGS = -O2 -Wall -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 $(RPM_OPT_FLAGS) then recompile and install dos2unix as before. Could you let me know if it makes a difference? Erwin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#614360: dos2unix doesn't work on windows 2003/2008 shares with debian 6.x
On 02/25/2011 03:28 PM, Dirk Haller wrote: Hi Erwin, good news...changing the Makefile did the trick. Both systems are 32bit, i am sorry but i don't have a debian 64bit system available at the moment. I can install a 64bit system next week and test it again, if that would be helpful? Hi Dirk, That is good to hear. I make that option default in the next version. If both systems are 32 bit, I don't understand why this problem only appears on Debian 6. I would expect this problem only when you are on a 32bit Linux and the files are larger than 2GB. (I assumed your test files are smaller.) And it is still strange it happens only on win2k3 and win2k8 shares, and not on win2000 shares. With _FILE_OFFSET_BITS=64 defined gcc will use the 64 bit file system interface. This makes it possible to open files larger than 2GB on a 32 bit system, provided that the OS has Large File Support (LFS) builtin (which Linux has). On a 64 bit Linux the file system interface is always 64 bit. You will not see the problem on a 64 bit Linux. You don't need to test this for me. I'm glad it worked, but I don't understand why you need the 64 bit interface for win2k3 and win2k8 shares. best regards, Erwin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#614360: dos2unix doesn't work on windows 2003/2008 shares with debian 6.x
Hi Dirk, I expected that the mode was printed for all files. Somehow only the mode of the first file test2k.txt is printed. Could you try again, running dos2unix only on the problematic files? /root/bin/dos2unix /mnt/temp/win2k3-share/test2k3.txt /root/bin/dos2unix /mnt/temp/win2k8-share/test2k8.txt I replaced dos2unix-5.2.1-beta2.tar.gz with an update about one hour after my previous message to this bug report. If you downloaded this file shortly after my previous message, it could be you need to download it again. If dos2unix-5.2.1-beta2.tar.gz is 51880 bytes, you have the latest version. Debian 5.0.7 used a different version of dos2unix. It could be that if you compile this version of dos2unix on Debian 5.0.7 you get the same problem there. It would be interesting to know. Erwin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#614360: dos2unix doesn't work on windows 2003/2008 shares with debian 6.x
Hi Dirk, Debian 5.0.7 uses a different implementation of dos2unix (tofrodos) which doesn't perform the check. That explains the difference in behaviour. Your quick workaround is to use the -f option on Debian 6. Option -f will force conversion. dos2unix -f w2k3.txt Could you try the latest dos2unix? Download http://www.xs4all.nl/~waterlan/dos2unix/dos2unix-5.2.1-beta2.tar.gz Unpack and compile a local version with DEBUG=1. make clean install DEBUG=1 prefix=$HOME Then use this version of dos2unix: $HOME/bin/unix2dos /mnt/temp/win2k-share/test2k.txt /mnt/temp/win2k3-share/test2k3.txt /mnt/temp/win2k8-share/test2k8.txt Could you give the output? regards, Erwin Waterlander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#614360: dos2unix doesn't work on windows 2003/2008 shares with debian 6.x
Hi, The code to test if a file is a regular file or not has not changed since I introduced it in dos2unix version 4.1. I suspect that something else is causing this change of behaviour. What is the output of these commands on Debian 6.0 and 5.0.7.? stat /mnt/temp/win2k3-share/test2k3.txt stat /mnt/temp/win2k-share/test2k.txt stat /mnt/temp/win2k8-share/test2k8.txt -- Erwin Waterlander Eindhoven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#518132: wcd: [Debian] Bug#518132: Suggestion to store files under ~/.wcd/
Op 12-10-10 22:37, Jari Aalto schreef: 1) In some specific environment where $HOME are readable inside a company, it may be desireable to be able to access other user's configurations. It's just that in today's environment, the user accounts are pretty much locked in elsewhere, so accessing other user's config for typical university or polytechnic, or other non-corporate environments in useually discouraged by policy. My experience is inside a company, where people work together on projects. Typical $HOME is open for the group and closed for the world. It's daily practice to read files from colleagues in your own group. What I also see a lot is that $HOME is open for the world and subdirectories are selectively closed for others or group (like I do). So I can share files with people in my company who are not part of my unix group. So, I don't know is large user base would be affected if the default were chnaged to use ~/.wcd and if not found, then revert back to the old. But an old version of wcd will not understand this. It will look for the old file locations and fail. In companies people are often conservative about software and operating systems. Upgrades are only done when absolutely needed. I see a lot of people using very old versions of wcd. They copy it to other colleagues. Some others use a new version. Wcd is not part of the OS, it are all individual installs. 2) The $HOME has been littering over the years as more and more software put stuff under $HOME. This makes managing home a challenge. The root of $HOME is worst place to put things. Although conveient for few configurations, it starts to be annoying for 100-200 configurations files. Trading typicaly two or three wcd files for one directory does not bring much advantage. I have 276 hidden files and directories in my $HOME (at work). I never felt annoyed by it. The probelem: You can't version control each package's configs separately very easily if it puts directly to $HOME. But if package writes to $HOME/.package/ that directory can be esily - Backed up I don't see a problem or why it makes a difference. We have all files automatically backed up regularly in .snapshot directories. Also when you backup up on tapes, all files under $HOME are included. - put under version control For me it's hard to imagine why anyone would like to put the .wcd files under version control. These are not source files. A backup suffices. The configuration of how wcd behaves is defined in the shell startup files, where people add options to the wcd function, or set environment variables. These are also in $HOME. - scp'd somewhere else to make a copy I don't see the difference in copying a hidden file or directory. Typically you don't copy these files. Wcd tree files belong to the file system where they are located on. A tree file, or alias, or stack file makes no sense on a different file system with different paths. People only copy the wcd settings in the shell startup file. It also makes overall management simples when there would be always a directory (C.f how ~/.ssh/ manages files. SUMMARY So, if you could ponder this and perhaps consider how the change would help the future needs. I will keep it in mind. I do agree that keeping by default all files under ~/.wcd is cleaner. But considering the small amount of files I rather keep it the way it is, so users are not bothered. I think that more people will be annoyed if I change this, compared to people who are annoyed by the amount of hidden files under $HOME. best regards, Erwin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521285: wcd: [Debian open Bug] path names are recoded in absolute form - use tilde(~)
Hi, This is fixed in wcd 5.1.3. This was already fixed in version 5.1.0 (Oct 22 2009). With a restriction that it only works for directories under $HOME. When $HOME is mounted to some absolute path, by the Volume Manager or auto-mounter, wcd will replace that absolute path with the value of $HOME. -- Erwin Waterlander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#518132: wcd: [Debian] Bug#518132: Suggestion to store files under ~/.wcd/
Hi, I'm still not in favour of implementing this. I want wcd to stay backwards compatible. Old and new versions must be able to be used together in a multi user environment. I agree that the choice I made in the past (1996) was not ideal. It would be nicer to have all files under ~/.wcd, or named the files .wcd.* instead of .*.wcd. But I have had never any other report from people who had a problem with it. And there is always the option to use $WCDHOME. It's only about a few files. I think I make more people happy by keeping it the way it is. -- Erwin Waterlander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521285: Debian bug#521285 wcd: path names are recoded in absolute form - use
Hi Jari, I recall this problem. Indeed, it has not been solved yet. My focus was lately on support for UTF-8 Unicode, which by now that is pretty stable. It looks like that this problem is typical for Solaris combined with the use of SVM (Solaris Volume Manager). And there is a workaround, so it didn't have high priority. It is still on my todo list. I can't predict when it will be solved. I think after I have finished support for UTF-16 Unicode on which I'm working now. best regards, -- Erwin Waterlander Zeelsterstraat 59B 5652 EB Eindhoven http://www.xs4all.nl/~waterlan/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521285: wcd: path names are recoded in absolute form - use tilde(~)
Jari Aalto schreef: Erwin Waterlander water...@xs4all.nl writes: $HOME/ Not ~/ Yes, those two are the same from interactive shell's perspective Yes. I want to store them as $HOME/. I want to fix this after 5.0.0 That's good news. Thankk you (for the script as well), Jari Hi, I think the issue has nothing to do with the automounter, but with Solaris Volume Manager (SVM). An automounter mounts typically under /tmp_mnt/. -- Erwin Waterlander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521285: wcd: path names are recoded in absolute form - use tilde(~)
Op 26-3-2009 17:57, Jari Aalto schreef: Erwin Waterlander water...@xs4all.nl writes: Op 26-03-09 17:04, Jari Aalto schreef: Why would you ask for a tilde if $HOME has more benefits? $HOME will work in all cases, and for you personal there is no difference in wcd usage. I think tilde should be used only inside the shell, not by programs. I probably misundestood. You mean that the paths were stores as: $HOME/ Not ~/ Yes, those two are the same from interactive shell's perspective Thanks for clarifying, Jari Yes. I want to store them as $HOME/. I want to fix this after 5.0.0. In the mean time you can do the following work around: Run a sed script on the tree data files after disk scanning scanning. Replace the automounter path with the value of $HOME. best regards, Erwin -- Erwin Waterlanderwater...@xs4all.nl Zeelsterstraat 59B, 5652 EB Eindhoven, The Netherlands www: http://www.xs4all.nl/~waterlan/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521285: wcd: path names are recoded in absolute form - use tilde(~)
Op 27-03-09 09:57, Erwin Waterlander schreef: I want to fix this after 5.0.0. In the mean time you can do the following work around: Run a sed script on the tree data files after disk scanning scanning. Replace the automounter path with the value of $HOME. And add to your wcd function something like this (before wcd.go is sourced). perl -pli -e s#/mnt/nfs/sripe-server/home/user/staff/depatment-xx/j/ja/jaalto#$HOME# ~/bin/wcd.go Erwin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521285: wcd: path names are recoded in absolute form - use tilde(~)
Op 26-03-09 14:24, Jari Aalto schreef: Package: wcd Version: 3.2.0-1 Severity: normal Wcd records information using absolute path names: $ cd ~/some/project/tree/deep/here $ wcd -l Enter alias for current directory: test $ cat $WCDHOME/.alias.wcd /mnt/nfs/sripe-server/home/user/staff/depatment-xx/j/ja/jaalto/some/project/tree/deep/here And this happens: $ wcd test /mnt/nfs/sripe-server/home/user/staff/depatment-xx/j/ja/jaalto/some/project/tree/deep/here$ Notice the prompt, where cursor sithe to the rightmost of ($). The typical bash setting contains the path name '\w' to keep track of current directory: $ echo $PS1 \...@\h \w\$ SUGGESTION Please substitute all path names so that the tilde(~) is used instead of absolute path name. To my understanding all interactive *user* shells (csh, tcsh, bash, ksh, pdksh etc.) support tilde expansion, so this should not create interactive use problems. Alternativey add new configuration option that would export path using tilde. This idea would be same as applying following code, before storing the PATH information: pwd | sed s,$HOME,~, Naturally implement in C, using getenv(HOME) ans some string manipulation. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wcd depends on: ii libc6 2.9-4 GNU C Library: Shared libraries ii libncurses5 5.7+20081213-1 shared libraries for terminal hand wcd recommends no packages. wcd suggests no packages. -- no debconf information Wcd will report the same path as `/bin/pwd', and that is different than the shell builtin `pwd' command. For instance if you cd to a soft link that is a link to a directory `pwd' will report a different path than `/bin/pwd'. Wcd has no access to the shell builtin commands. That is also the reason why the wcd executable cannot change directory, and we have to do a trick with a shell function. Replacing $HOME with ~ will not work in multi-user environments if people start reading each others .wcd files. ~ has a different meaning for every user. It looks like that on your system the auto mounter has mounted your $HOME to /mnt/nfs/sripe-server/home/user/staff/depatment-xx/j/ja/jaalto What path do you get if you type `pwd' and `/bin/pwd' in your $HOME directory? Wcd assumes a default way of working of the auto mounter, that all HOME directories are auto mounted in /tmp_mnt/. For instance my HOME dir is mounted to /tmp_mnt/home/waterlan In my HOME dir the output of pwd is as follows: pwd /home/waterlan /bin/pwd /tmp_mnt/home/waterlan Wcd will also see /tmp_mnt/home/waterlan, but automatically strips /tmp_mnt from the path. The /tmp_mnt string is hard coded in Wcd. Perhaps it is better to make this configurable. best regards, Erwin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521285: wcd: path names are recoded in absolute form - use tilde(~)
Op 26-03-09 15:25, Jari Aalto schreef: Erwin Waterlander water...@xs4all.nl writes: It looks like that on your system the auto mounter has mounted your $HOME to /mnt/nfs/sripe-server/home/user/staff/depatment-xx/j/ja/jaalto What path do you get if you type `pwd' and `/bin/pwd' in your $HOME directory? The example was under SunOs, where I have no control. Wcd will report the same path as `/bin/pwd', and that is different than the shell builtin `pwd' command. For instance if you cd to a soft link that is a link to a directory `pwd' will report a different path than `/bin/pwd'. Understood. ... Alternatively add new configuration option that would export path using tilde. I'd gladly resolve to the alternate solution, where user can ask the program to do the conversion. Most user's use wcd() for their personal files, where the tilde(~) solution works; with caveats that can be expressed in manual page when the option is used. Jari Hi, I rather assume nothing. I don't know if tilde works in any (old) shell. It doesn't work in DOS/Windows shells, that's for sure. I can't ignore that. I know that absolute paths always work, on any system, in any shell. If the auto mounter path is replaced with your $HOME path than the problem is solved, isn't it? Do you really need the tilde? `/home/jaalto' is good, I think. It is also better in a multi-user environment than ~/. Erwin
Bug#521285: wcd: path names are recoded in absolute form - use tilde(~)
Op 26-03-09 17:04, Jari Aalto schreef: Erwin Waterlander water...@xs4all.nl writes: ... Alternatively add new configuration option that would export path using tilde. I rather assume nothing. I don't know if tilde works in any (old) shell. It doesn't work in DOS/Windows shells, that's for sure. I can't ignore that. I know that absolute paths always work, on any system, in any shell. When this is an optional feature, which is requested by user via an option, it's up to the user to get what he asks. In personal accounts this will would work quite well. Jari Why would you ask for a tilde if $HOME has more benefits? $HOME will work in all cases, and for you personal there is no difference in wcd usage. I think tilde should be used only inside the shell, not by programs. Erwin
Bug#518136: wcd: reverse options -v -V
Op 23-03-09 18:04, Jari Aalto schreef: [GNU long options] I'd like to propose another approach. It would be possible to use: #ifdef HAS_GNU_GETOPT at compile time to offer --long options for those platforms that have the GNU libraries installed. Would you accept a patch for this? I will add --help, --version and --verbose. Without using getopt. My conclusions are: * There exists no standard that prescribes -v for verbose or -V for version * There is no tradition to use -v for verbose. * GNU only standardised some long options. * Many GNU programs use -v for verbose and -V for version. * Many programs (also with GNU license) use -v for version. For me this is a non-issue. I will switch options -v and -V. Using long options for Wcd would be joke, because wcd is all about reducing typing. My motivation was that, Open Source software could become better whe quality is improved. One part of the quality is that programs behave consistently using similar command line options; when they can be genrally agreed on. The standards are what we make of them. Thank you for the change, small it may be, it's an important step. Jari To standardise you need a standard. There is no standard that prescribes single letter command line options, so it will be a though job to convince everybody. I think there is a good reason that this has not been standardised. Programs are very different and are used in a different context. They can have good reasons to do it different. A single letter can be an abbreviation of anything, even if you restrict it to English language only. With my local wcd build I have typed now already several times wcd -v, while I should type wcd -V. Thousands of wcd users will also make this mistake when the next version is released. I don't like bothering users... But this doesn't break core functionality, so it is not so bad. best regards, Erwin Waterlander
Bug#518136: wcd: reverse options -v -V
Op 22-03-09 16:21, Jari Aalto schreef: Erwin Waterlander water...@xs4all.nl writes: It's a bit difficult to follow top-posted emails, when the conversation does not flow naturally. From user perspective, unifying the command line options would be a good thing, thus I propose moving forward with -v, --verbose and -V, --version as they are also GNU standards. I have not searched much, but what I have seen so far is that Gnu standardises only on the long options. See http://www.gnu.org/prep/standards/html_node/Command_002dLine-Interfaces.html Can you point me to a document about standardised short options? We can observe the use of equivalent short options in GNU programs (as shows in previous messages). The utilities that are used daily, those of: cp -v mv -v ssh -v -v ... determine what is is the interpreted meaning of lowercase -v. many use that daily to mean verbose It should not be a big switch for other programs to follow similar convention. A more consistent interface would be welcomed in all aspects. Those other programs that you referred to, that use -v differently, would be welcomed to change accordingly. Jari Hi, Eric S. Raymond writes in his The Art of Unix Programming a list of single letter options which are not uncommon to experienced Unix users (http://www.faqs.org/docs/artu/ch10s05.html). In this list -v is for verbose and -V for version number as you propose. This document is not a specification, but the experience of Eric. My experience is different. Option -v for verbose etc is only standard on GNU applications is my 14 year experience. When you are not on Linux, but on a commercial Unix version, everything is different. POSIX does not prescribe any specific option (see http://www.iam.ubc.ca/guides/javatut99/essential/attributes/_posix.html). GNU only standardises the long options as I already mentioned. X toolkit does it also different. Wcd is used also by many people who work on Unix (not Linux), who are not used to GNU command line options. In the beginning I used wcd many years on HP-UX and Solaris. For a long time I have been thinking to use the getopt() function, but two issues stopped me from doing it. * The function is often not included if you use an other compiler than gcc. So I had to include getopt() in my source. I found it too big. * I use besides the hyphen also the plus switch. My conclusions are: * There exists no standard that prescribes -v for verbose or -V for version * There is no tradition to use -v for verbose. It may look like a tradition for people who have only used Linux and GNU applications. * GNU only standardised some long options. * Many GNU programs use -v for verbose and -V for version. * Many programs (also with GNU license) use -v for version. For me this is a non-issue. I will switch options -v and -V. Using long options for Wcd would be joke, because wcd is all about reducing typing. best regards, Erwin Waterlander
Bug#518136: wcd: reverse options -v -V
Op 23-03-09 10:12, Erwin Waterlander schreef: Op 22-03-09 16:21, Jari Aalto schreef: Erwin Waterlander water...@xs4all.nl writes: It's a bit difficult to follow top-posted emails, when the conversation does not flow naturally. From user perspective, unifying the command line options would be a good thing, thus I propose moving forward with -v, --verbose and -V, --version as they are also GNU standards. I have not searched much, but what I have seen so far is that Gnu standardises only on the long options. See http://www.gnu.org/prep/standards/html_node/Command_002dLine-Interfaces.html Can you point me to a document about standardised short options? We can observe the use of equivalent short options in GNU programs (as shows in previous messages). The utilities that are used daily, those of: cp -v mv -v ssh -v -v ... determine what is is the interpreted meaning of lowercase -v. many use that daily to mean verbose It should not be a big switch for other programs to follow similar convention. A more consistent interface would be welcomed in all aspects. Those other programs that you referred to, that use -v differently, would be welcomed to change accordingly. Jari Hi, Eric S. Raymond writes in his The Art of Unix Programming a list of single letter options which are not uncommon to experienced Unix users (http://www.faqs.org/docs/artu/ch10s05.html). In this list -v is for verbose and -V for version number as you propose. This document is not a specification, but the experience of Eric. My experience is different. Option -v for verbose etc is only standard on GNU applications is my 14 year experience. When you are not on Linux, but on a commercial Unix version, everything is different. POSIX does not prescribe any specific option (see http://www.iam.ubc.ca/guides/javatut99/essential/attributes/_posix.html). GNU only standardises the long options as I already mentioned. X toolkit does it also different. Wcd is used also by many people who work on Unix (not Linux), who are not used to GNU command line options. In the beginning I used wcd many years on HP-UX and Solaris. For a long time I have been thinking to use the getopt() function, but two issues stopped me from doing it. * The function is often not included if you use an other compiler than gcc. So I had to include getopt() in my source. I found it too big. * I use besides the hyphen also the plus switch. My conclusions are: * There exists no standard that prescribes -v for verbose or -V for version * There is no tradition to use -v for verbose. It may look like a tradition for people who have only used Linux and GNU applications. * GNU only standardised some long options. * Many GNU programs use -v for verbose and -V for version. * Many programs (also with GNU license) use -v for version. For me this is a non-issue. I will switch options -v and -V. Using long options for Wcd would be joke, because wcd is all about reducing typing. best regards, Erwin Waterlander Hi, Options -v and -V have been switched. I also changed -Q into -q (-q was used for an other purpose long time ago). Changes have been committed to subversion repository and will be in next release. Erwin
Bug#518136: wcd: reverse options -v -V
Hi, I have not searched much, but what I have seen so far is that Gnu standardises only on the long options. See http://www.gnu.org/prep/standards/html_node/Command_002dLine-Interfaces.html Can you point me to a document about standardised short options? Wcd does not use long options. Wcd does also not use 'getopt()' to parse the commands. I found getopt() too big for the 16 bit DOS version of wcd (there are still many dos 16bit users). And wcd uses also the '+' switch in addition to the '-' switch. The '+' switch is not supported by getopt(). But I think it's good to follow gnu guidelines. In that sense Wcd should support long options and it would be good to support options --help, --version and --verbose. I still can't agree that there is a world wide tradion wrt -v. Another example: konsole (KDE Terminal) also uses -v for version info. Perhaps a lot more KDE progams do. There is no real standard for the short options, is my opinion. I have encountered many times programs that don't even support '-h' for help. Also don't forget that the world of software is much bigger than Gnu software alone. best regards, Erwin Jari Aalto schreef: There are also plenty of programs that use -v for version info. E.g. zip, mutt, pine, troff, nroff, firefox, thunderbird, file, strings, kcd ... also programs that use -V for verbose. E.g. vim. In the world of software, programs are written without any contact between various authors. It would help if as many programs as possible standardize to known conventions, where I believe (-v, --verbose) is more universally used. E.g. in n daily basis e.g. in ssh(1) and GNU commands. From user perspective, unifying the command line options would be a good thing, thus I propose moving forward with -v, --verbose and -V, --version as they are also GNU standards. Every detail, options and good manual pages are important for improving the quality of software. Thank you for bringing up the other programs, we hope to see those programs standardize their command line options as well (Bug reports under way). Jari -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#518280: wcd: Make options -l accept second arg as ALIAS-NAME (not ask interactively)
Hi Jari, This has been implemented. Committed to svn and a beta3 tar file is available. http://www.xs4all.nl/~waterlan/wcd-4.1.1-beta3-src.tar.gz best regards, Erwin Op 05-03-09 10:47, Erwin Waterlander schreef: I agree. Erwin Waterlander Op 05-03-09 09:33, jaalto schreef: Package: wcd Version: 3.2.0-1 Severity: wishlist Current behavior: $ cd to/path $ wcd -l my-alias = Wcd: Enter alias for current directory: SUGGESTION Instead of asking the alias name from the user, it would be nice if the second argument after -l were parsed as alias name directly. -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wcd depends on: ii libc6 2.7-18 GNU C Library: Shared libraries ii libncurses5 5.7+20081213-1 shared libraries for terminal hand wcd recommends no packages. wcd suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#518222: wcd: option -a adds PATH multiple times to treedata.wcd
Jari Aalto schreef: Erwin Waterlander water...@xs4all.nl writes: wcd -a wcd -a cat ~/.treedata.wcd This is not a problem. Duplicate entries in the data file don't result in duplicate matches, because duplicate matches are filtered out. I understand that this is not a problem in the program, but it is presents a problem for the user side: 1. Put directory $WCDHOME into version control (take your pick: RCS, Cvs, Svn, Hg, Bzr, Git ...) Any chnage since last save to version control will be reported modified sources. 2. Add same directory again wcd -a = Not the .treedata.wcd has now changed content = Version control reports changed files committing to version scontrol would be wrong thing to do. The multiple entries effective prevent using version control effectively to save the states. If the program checked the entry before adding it to file, the WCDHOME would stay pristine. Why would anyone add wcd data files to a version control system? If you have 1TB disk and 100 wcd's, you do want to have backup. And you want to notice chnages. Version does incremental backup control efficiently with added binus that you can tag the versions and compare chnages since etc. I also don't expect that a user types 'wcd -a' twice. The program does what the user asks it to do. Wcd is as intelligent as the user. The program should not add entry twice. It is better to: 1) substitute the old entry with new 2) *or* warn the user about existing entry with the same name, Consider variable assignment: a=1 a=3 There is no two a's. Analogous to 'alias' commands in shells: alias ll=ls -l alias ll=ls -la Jari Hi Jari, On such big systems directories change every day. I work in such an environment with a huge amount of disk space on file servers. I have a cron job scheduled which starts a wcd scan every night. Data backup is not done with version control software like users use in a project. It is done with a snapshot system. It also stores incremental changes and now and then a full copy. Snapshots are made multiple times per day. Huge amounts of files are handled and among them are huge files. The impact of this wcd optimisation on the snapshot system is neglectible. It is extremely tiny. And the occasion that people type wcd -a twice in the same path is already rare. If I would implement the optimisation for option -a I have to do it also for option -A which is used a lot. For every path I add I have to do a check. This slows down scanning of a directory tree. I think it is better to have faster scanning instead of an optimisation which is neglectable. best regards, Erwin Waterlander
Bug#518132: wcd: Suggestion to store files under ~/.wcd/
Jari Aalto schreef: ~/.wcd/ I agree. It would be cleaner. But I don't like it that the backward compatibility is broken. Wcd has been backward compatible since the start, that is over 12 years. I don't think there would be compatibility issues: - IF there is WCDHOME use it - IF there is ~/.treedata.wcd file, use old behavior - ELSE use new scheme, where data is put under ~/.wcd/ New format would appear only for new users. Or, if people prefer, they could migrate manually as instructed in to be manual page: mkdir ~/.wcd/ mv ~/.[a-z]*.wcd ~/.wcd/ Jari People who use an old version of wcd have a problem if they want to jump to folders of people who use the new version. Old wcd will still look for ~/.treedata.wcd of other user. He may be reading an obsolete file it does exist, or find no file at all. This is an issue. New wcd should first check in ~/.wcd/ and then in ~/ of other user. Assuming that if both files exist the other user probably uses the new wcd. For new wcd users there is no issue. Erwin
Bug#518222: wcd: option -a adds PATH multiple times to treedata.wcd
Hi, Why would anyone add wcd data files to a version control system? The default tree data file is personal. I have never seen people adding personal settings to a project's version control system. I also don't expect that a user types 'wcd -a' twice. The program does what the user asks it to do. Wcd is as intelligent as the user. Erwin Op 05-03-09 17:29, Jari Aalto schreef: Erwin Waterlander water...@xs4all.nl writes: wcd -a wcd -a cat ~/.treedata.wcd This is not a problem. Duplicate entries in the data file don't result in duplicate matches, because duplicate matches are filtered out. I understand that this is not a problem in the program, but it is presents a problem for the user side: 1. Put directory $WCDHOME into version control (take your pick: RCS, Cvs, Svn, Hg, Bzr, Git ...) Any chnage since last save to version control will be reported modified sources. 2. Add same directory again wcd -a = Not the .treedata.wcd has now changed content = Version control reports changed files committing to version scontrol would be wrong thing to do. The multiple entries effective prevent using version control effectively to save the states. If the program checked the entry before adding it to file, the WCDHOME would stay pristine. Jari
Bug#518132: wcd: Suggestion to store files under ~/.wcd/
Hi, I agree. It would be cleaner. But I don't like it that the backward compatibility is broken. Wcd has been backward compatible since the start, that is over 12 years. In enterprise network systems people use the -u option to jump to directories of colleagues. If you move data files you break this functionality, because there are still people using older versions of wcd. I see it also at my work. People keep on using old versions for long time. I want to bother them to upgrade. Such systems can have hundreds of users, and you have no control, about which version of wcd they use. Also many users will have to move custom made tree files. There are even people who build scripts around wcd. I want to keep them happy. ``Software is like sex. Make one mistake, and support it for the rest of your life.'' ;-) This was not a big mistake. It's only about a few files. I prefer keeping people happy. Erwin Op 05-03-09 13:23, Jari Aalto schreef: Erwin Waterlander water...@xs4all.nl writes: The amount of data that is stored by for instance Mozilla under ~/.mozilla is enormous ... There are many application that only have few files. Exerpts: [DIR] ~/.ccache/: CACHEDIR.TAG stats [DIR] ~/.dillo/: adblock.txt cookiesrc cookies.txt dpi_socket_dir [DIR] ~/.gstreamer-0.10/: registry.i486.xml registry.x86_64.bin [DIR] ~/.putty/: sshhostkeys [DIR] ~/.VirtualBox/: compreg.dat VirtualBox.xml xpti.dat [DIR] ~/.xfe/: trash xferc ... The point is not, how many. It's more clean to have each application to reserve its own directory ~/.application 1/ ~/.application 2/ ~/.application 3/ In my $HOME directory I have 244 hidden files and directories. ls -a | grep '^\.' | wc -l 244 Most wcd users will have only 2 .wcd files in $HOME... From the original report: Any help managing that is welcomed. There are benefits in separate dirs: - backup by directory - version control by directory - ignore directories from searches; find(1) etc. Jari
Bug#518136: wcd: reverse options -v -V
Hi, There are also plenty of programs that use -v for version info. E.g. zip, mutt, pine, troff, nroff, firefox, thunderbird, file, strings, kcd I could go on if I searched more... And there are also programs that use -V for verbose. E.g. vim. But you may be right. There may be more programs that do it the other way around these days. I haven't counted. I don't think that you can speak of a general tradition. Isn't this a non-issue? Erwin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#518222: wcd: option -a adds PATH multiple times to treedata.wcd
Hi, This is not a problem. Duplicate entries in the data file don't result in duplicate matches, because duplicate matches are filtered out. Also in graphical tree mode duplicates are filtered out. With the option -A you can add even complete directory trees multiple times. Duplicate entries in the data file have no noticeable impact on the performance of wcd. best regards, Erwin Op 04-03-09 22:15, jaalto schreef: Package: wcd Version: 3.2.0-1 Severity: normal Example: cd to/path wcd -a wcd -a cat ~/.treedata.wcd The to/path is added multiple times to the data file. -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wcd depends on: ii libc6 2.7-18 GNU C Library: Shared libraries ii libncurses5 5.7+20081213-1 shared libraries for terminal hand wcd recommends no packages. wcd suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#518280: wcd: Make options -l accept second arg as ALIAS-NAME (not ask interactively)
I agree. Erwin Waterlander Op 05-03-09 09:33, jaalto schreef: Package: wcd Version: 3.2.0-1 Severity: wishlist Current behavior: $ cd to/path $ wcd -l my-alias = Wcd: Enter alias for current directory: SUGGESTION Instead of asking the alias name from the user, it would be nice if the second argument after -l were parsed as alias name directly. -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wcd depends on: ii libc6 2.7-18 GNU C Library: Shared libraries ii libncurses5 5.7+20081213-1 shared libraries for terminal hand wcd recommends no packages. wcd suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#518132: wcd: Suggestion to store files under ~/.wcd/
Hi, Wcd already supports an alternative location via the WCDHOME environment variable. Setting this variable will do what is suggested for WCD_ROOT. Many programs use a $HOME sub directory for configuration files, but many more use by default just $HOME. Since files are hidden it's not a big hinder. The number of files is not so big. By default you have only two (.treedata.wcd and .stack.wcd). The other three are optional (.alias.wcd .ban.wcd .extra.wcd). I see wcd as an enhancement of the shell which has also all its files in $HOME (.bashrc, .profile, .bash_login, ...) Because $HOME is usually defined on unix/linux it simplifies the installation. I would like to stay backwards compatible, so people don't need to move their custom wcd files if they upgrade. The grand old NCD used to store its tree info in the root of the drive. On unix this is comparable to $HOME for a user (on enterprise systems). best regards, Erwin Waterlander Op 04-03-09 11:46, jaalto schreef: Package: wcd Version: 3.2.0-1 Severity: wishlist The manual page lists: FILES default treedata file UNIX: $HOME/.treedata.wcd This is the default treedata file where wcd searches for matches. If it is not readable wcd will create a new one. extra treedata file UNIX: $HOME/.extra.wcd An optional extra treedata file. If it exists and is readable wcd will try to find matches in this file also. ... SUGGESTION The HOME directory is quite crowded and it would be desireable if application stored the FILES (cf. manual page) under its own directory. Please store all files under user defined environment variable: WCD_ROOT When undefined, program would default to: $HOME/.wcd/ ERROR CONDITIONS If WCD_ROOT does not exist, program terminates and displays an error. If default directory $HOME/.wcd/ does not exist, it is created. This is typical behaviour (Cf. ~/.mozilla/ ~/.opera/ ...). -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wcd depends on: ii libc6 2.7-18 GNU C Library: Shared libraries ii libncurses5 5.7+20081213-1 shared libraries for terminal hand wcd recommends no packages. wcd suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#518132: wcd: Suggestion to store files under ~/.wcd/
Hi, The amount of data that is stored by for instance Mozilla under ~/.mozilla is enormous compared to the few files of wcd. Logically you don't want all Mozilla's files in your $HOME folder. In my $HOME directory I have 244 hidden files and directories. ls -a | grep '^\.' | wc -l 244 Most wcd users will have only 2 .wcd files in $HOME. I you remove those and add a .wcd directory, the amount goes down by 1. If it is common to have over 200 hidden files and directories in $HOME, the impact is less than 0.5% in most cases. Is it really worth the effort? I don't mind having 244 or 240 hidden files in $HOME. And the user always has the option to use WCDHOME if he/she doesn't like the files in $HOME. best regards, Erwin Op 04-03-09 14:37, Jari Aalto schreef: Erwin Waterlander water...@xs4all.nl writes: Hi, Wcd already supports an alternative location via the WCDHOME environment variable. Noticed, that'd why I adjusted the bug report accordingly. The Login shells are exception. Other programs would better use ~/.program/ An example: my $HOME contains ls -a | grep '^\.' | wc -l 204 Any help managing that is welcomed. There are benefits in separate dirs: - backup by directory - version control by directory - ignore directories from searches; find(1) etc. Jari --- Clarification to the previous bug report. wcd(1) contains variable WCDHOME, so please treat (*) marked as follows: Please store all files under user defined environment variable: *) forget this WCD_ROOT *) implement this When undefined, program would default to: $HOME/.wcd/ *) implement these ERROR CONDITIONS If WCD_ROOT does not exist, program terminates and displays an error. If default directory $HOME/.wcd/ does not exist, it is created. This is typical behaviour (Cf. ~/.mozilla/ ~/.opera/ ...).
Bug#517334: wcd: [manual] nroff URL, hyphenation and section order fixes
Hi, Changes have been committed to svn. I released wcd-4.1.1-beta2. http://www.xs4all.nl/~waterlan/wcd-4.1.1-beta2-src.tar.gz best regards, Erwin Op 27-02-09 08:52, Erwin Waterlander schreef: Hi Jari, Thanks for the improvements. I will include them in version 4.1.1. I'm waiting for a Spanish translation and then I'm going to release 4.1.1. I will commit the changes to the svn repository at Sourceforge for early access. best regards, Erwin Op 27-02-09 02:02, jaalto schreef: Package: wcd Version: 3.2.0-1 Severity: wishlist Tags: patch Here are some improvements for the manual page for (upcoming) 4.1.0: - The URLs are too long for nroff. Those are now fixed with correct formatting code - The /path/names are best not to be hyphenated. Those are now fixed with correct formatting code - The order of sections is chnages to follow de facto section order http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap01.html#tag_01_11 - The quotes `` '' are escaped to make clean output. - The top-level INSTALL sections are not made subsections for more clearer layout. Attached files include: - The patch against 4.1.0 - The new corrected wcd.1 manual page -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wcd depends on: ii libc6 2.7-18 GNU C Library: Shared libraries ii libncurses5 5.7+20081213-1 shared libraries for terminal hand wcd recommends no packages. wcd suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#517334: wcd: [manual] nroff URL, hyphenation and section order fixes
Hi Jari, Thanks for the improvements. I will include them in version 4.1.1. I'm waiting for a Spanish translation and then I'm going to release 4.1.1. I will commit the changes to the svn repository at Sourceforge for early access. best regards, Erwin Op 27-02-09 02:02, jaalto schreef: Package: wcd Version: 3.2.0-1 Severity: wishlist Tags: patch Here are some improvements for the manual page for (upcoming) 4.1.0: - The URLs are too long for nroff. Those are now fixed with correct formatting code - The /path/names are best not to be hyphenated. Those are now fixed with correct formatting code - The order of sections is chnages to follow de facto section order http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap01.html#tag_01_11 - The quotes `` '' are escaped to make clean output. - The top-level INSTALL sections are not made subsections for more clearer layout. Attached files include: - The patch against 4.1.0 - The new corrected wcd.1 manual page -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wcd depends on: ii libc6 2.7-18 GNU C Library: Shared libraries ii libncurses5 5.7+20081213-1 shared libraries for terminal hand wcd recommends no packages. wcd suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
