Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

SingIt Lyric Displayer 0.1.37 (Development branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News SingIt Lyric Displayer 0.1.37 (Development branch)
# 1  
Old 07-14-2008
SingIt Lyric Displayer 0.1.37 (Development branch)
ImageThe SingIt Lyric Displayer is a program to display formatted lyrics, including tagged text, CD+G, and id3v2xx lyrics. It consists of several displayers, an integrated editor, query, and karaoke tools. It supports various players, such as XMMS, Noatun, and Rhythmbox. License: GNU General Public License (GPL)Changes:
This release adds hyphenation support and Audacious integration, as XMMS isn't available anymore in the latest Debian/Ubuntu distributions. People using amarok should try this release, as the amarok plugin was updated and the lyrics should be better synchronized now.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. Infrastructure Monitoring

ZABBIX 1.5 (Development branch)

http://images.freshmeat.net/screenshots/13929_thumb.png ZABBIX is an enterprise-class distributed monitoring solution designed to monitor and track performance and availability of network servers, devices, and other IT resources. It supports distributed and Web-based monitoring, auto-discovery,... (0 Replies)
Discussion started by: Linux Bot
0 Replies
Login or Register to Ask a Question

LEARN ABOUT MOJAVE

git-request-pull

GIT-REQUEST-PULL(1)                                                 Git Manual                                                 GIT-REQUEST-PULL(1)

NAME

       git-request-pull - Generates a summary of pending changes

SYNOPSIS

       git request-pull [-p] <start> <url> [<end>]

DESCRIPTION

       Generate a request asking your upstream project to pull changes into their tree. The request, printed to the standard output, begins with
       the branch description, summarizes the changes and indicates from where they can be pulled.

       The upstream project is expected to have the commit named by <start> and the output asks it to integrate the changes you made since that
       commit, up to the commit named by <end>, by visiting the repository named by <url>.

OPTIONS

       -p
           Include patch text in the output.

       <start>
           Commit to start at. This names a commit that is already in the upstream history.

       <url>
           The repository URL to be pulled from.

       <end>
           Commit to end at (defaults to HEAD). This names the commit at the tip of the history you are asking to be pulled.

           When the repository named by <url> has the commit at a tip of a ref that is different from the ref you have locally, you can use the
           <local>:<remote> syntax, to have its local name, a colon :, and its remote name.

EXAMPLE

       Imagine that you built your work on your master branch on top of the v1.0 release, and want it to be integrated to the project. First you
       push that change to your public repository for others to see:

           git push https://git.ko.xz/project master

       Then, you run this command:

           git request-pull v1.0 https://git.ko.xz/project master

       which will produce a request to the upstream, summarizing the changes between the v1.0 release and your master, to pull it from your public
       repository.

       If you pushed your change to a branch whose name is different from the one you have locally, e.g.

           git push https://git.ko.xz/project master:for-linus

       then you can ask that to be pulled with

           git request-pull v1.0 https://git.ko.xz/project master:for-linus

GIT

       Part of the git(1) suite

Git 2.17.1                                                          10/05/2018                                                 GIT-REQUEST-PULL(1)