similar to: z shell completion for vorbiscomment

I've written a first version of a z shell completion function for the FLAC metadata editing program, metaflac; right now it doesn't complete any of the option arguments that arn't files, but it handles the various options, and handles looking only for FLAC files. I plan to implement completion for the tag options, so that, i.e. `metaflac foo.flac --show-tag=` would automatically

Hi guys, I had looked for help on the debian gis list, but given this thread and others (https://stat.ethz.ch/pipermail/r-sig-debian/2011-April/001590.html ), maybe someone here could assist. I’m looking a bit of guidance trying to install rgdal on a beowulf cluster where i don't have root access. I was able to successfully download the gdal binaries and compile it to my home

Hi all, I have successfully made and installed both gdal, and proj.4, but still cannot get rgdal to be installed in R. I think i'm very close. I do not have root access, if that matters, i've installed everything locally. I'm using debian on a beowulf cluster. I call: install.packages("rgdal", .libPaths()[1], configure.args =

On Thu, Nov 29, 2012 at 9:41 AM, Joe Abbey <jabbey at arxan.com> wrote: > I know this process is well documented here > http://llvm.org/docs/GettingStarted.html > > But man do I love scripting things: > > LLVM Getting Started (See http://llvm.org/docs/GettingStarted.html) > ./getttingStarted.sh [-clang] [-compiler-rt] [-test-suite] [-branch branch] > [-dir path] [-r

So instead of being able to quickly extend scripting via Bash or C Shell you'd prefer people learn Python to extend any functionality? Cygwin is well tested on Windows. Shell Scripting [Bash, C, Ksh, ZShell, etc] is pervasive in UNIX/Linux and won't be replaced by Python or Perl. Simple automated scripts requiring the memory footprint of python just to make it work in Windows seems

Erik, I was thinking of doing this: export MALLOC_PERTURB_=$(awk 'BEGIN { srand(); print int(rand() * 32767 % 255 + 1) }') Or would you prefer using 'date'? On Tue, Mar 19, 2013 at 10:22 PM, Erik de Castro Lopo <mle+la at mega-nerd.com>wrote: > Jesse Weinstein wrote: > > > The subject line mostly says it all, but for reference, having #!/bin/sh > causes

I think that vorbiscomment should really use -c "this=that" to specify tags on the commandline, consistent with oggenc. That displaces the tag source file, so I'd suggest -f, consistent with at least some other programs (although I can only think of tar, right now). I'd also suggest that it use -o for an output filename rather than splattering the second file on the

Hi all, I just committed some big changes to vcedit (the core of vorbiscomment, and also the core comment rewriting functionality used by a number of other programs (xmms, for instance). It's now able to handle several nasty cases that it couldn't before, but it may have new problems - so, everyone, go and throw nasty or broken input files at it, and see if it breaks. Please. And those

> While you are at it, can you check/fix the following warning > ? > > metadata.cpp:812:98: warning: narrowing conversion of > 'strlen(((const > char*)string))' from 'size_t {aka long unsigned int}' to > 'FLAC__uint32 > {aka unsigned int}' inside { } is ill-formed in C++11 > [-Wnarrowing] > > > Thanks ! Yeah sure! I don't get

Bastiaan Timmer wrote: > Attached is a patch that adds 5 missing Patch applied. Thanks. > Looking at the FLAC__metadata_object_cuesheet_* FLAC__metadata_ > object_picture_* functions, it looks like the corresponding FLAC++ > classes are already complete. Maybe some functions are missing from > CueSheet::Track. If nobody objects, I will take a look later this > week. Thanks.

Here's a patch that stops the flac binary from writing empty tag fields. At least in Windows world these come to files by accident. CD extraction programs pass all possible metadata entries they allow setting in the UI to flac binary and most of the time most fields are empty when basic info like artist, album, title, track number and release date are the only fields that are set.

David K. Gasaway wrote: > Daniel Aleksandersen wrote: >> On Monday 17. September 2007 07:47:19 David K. Gasaway wrote: >>> Even today, I use my own "metadata format" -- essentially a superset of >>> vorbis comments. There is one file per release, even with a multi-disc >>> release. As a final part of the ripping process, I apply this metadata

Hi, I guess you already know this, but src/plugin_common/vorbiscomment.h is missing from the 1.0.4beta tarball. The best thing would be to release a new beta ASAP, thanks. -- G?tz Waschk <> master of computer science <> University of Rostock http://wwwtec.informatik.uni-rostock.de/~waschk/waschk.asc for PGP key --> Logout Fascism! <--

Hi, I guess you already know this, but src/plugin_common/vorbiscomment.h is missing from the 1.0.4beta tarball. The best thing would be to release a new beta ASAP, thanks. -- G?tz Waschk <> master of computer science <> University of Rostock http://wwwtec.informatik.uni-rostock.de/~waschk/waschk.asc for PGP key --> Logout Fascism! <--

Hi I've a bug in vorbis-tools's libutf8 - some share/*.[ch] files don't include config.h; as a result, utf8.c:convert_set_charset doesn't try charset = nl_langinfo(CODESET) which would correctly return UTF-8, because HAVE_LANGINFO_CODESET isn't defined (it's defined in config.h, but config.h is not included). So, the bugfix is simple - just include config.h everywhere

" Ivo Emanuel Gon?alves " <justivo at gmail.com> wrote: ... > To be fair, only the Vorbis users requested albumart. FLAC users > should in theory be able to use the tag too if they want, but this > wouldn't be something we'd see in other codecs like Speex and Theora. This is a minor point, but FLAC users can already do this using METADATA_BLOCK_PICTURE (which

Some of these things may allready be addressed: Comments in oggfiles: (meaning the accutall keyword "comment(s)" With xmms you can edit oggtags, among artist and title you have "comment" * xmms creates comment attributes starting with "=" * freeamp does not seem to understand ogg-"comment" at all. * oggenc seems to like to put the comment as is without

First, the in the links section of www.vorbis.com is a link to http://www.vorbislinks.com/ which no longer a vorbis dedicated site (it's one of those general dns parking/general index). I don't know who's the webmaster, it is implied that's Simon Yorkston, but I'm not sure. Anyway, the real rason of this mail is that I'm ripping my CDs collection, and I'm taking a

Could someone please tell me what I'm doing wrong here? I have some oggs tagged using other applications and ogginfo doesn't give me any warnings when I use UTF-8 in them. I did the following: $ vorbiscomment --raw -a test.ogg -t "test=åäö" $ vorbiscomment --raw -l test.ogg test=åäö $ ogginfo -v test.ogg Processing file "test.ogg"... New logical stream (#1, serial:

I'm writing a couple of reader/writer functions for a music tag class for python that can read and write 'raw' vorbis comments to text files[1]. I want these text files to be basically the same as the output/input comments used by the vorbiscomment program, but while testing out multi line comments I discovered that while vorbiscomment can set them with a -t "tag=value"