Re: ;;; anything.el --- open anything
On Jul 21, 11:48 pm, Tassilo Horn <[EMAIL PROTECTED]> wrote: > "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes: > > Hi Tamas, > > >> That's nice, really nice. I'll have a lot of fun adding stuff to > >> anything-config.el. > > > BTW, don't you want to be in charge of anything-config.el? > > Yes, why not? I'll create a emacswiki page for anything.el tomorrow (if > the weather is as bad as the news said). > Okay, it's yours then. Others please contact Tassilo if you want your stuff integrated into anything-config.el BTW, anything-config might override some defaults too in addition to providing predefined sources and actions. anything-type-actions may be overriden safely, since it only provides actions for types and the list of actions for, say, files and buffers can have a sensible default. Just some random thought. I let you decide, since you're in charge. ;) ___ gnu-emacs-sources mailing list gnu-emacs-sources@gnu.org http://lists.gnu.org/mailman/listinfo/gnu-emacs-sources
file-props.el - new version
Time for a new version. I made it possible to coonfigure how multiple tags are read - I think everyone should be happy now :) Also added are a feature to display file properties (comment and tags) while navigating in Dired. Read more in the Commentary below. This version is also on EmacsWiki. Enjoy! /Mathias ;;; file-props.el --- Add file properties to your files ;; ;; Copyright (C) 2006, 2007 Mathias Dahl ;; ;; Version: 0.1.3 ;; Keywords: search, convenience, files ;; Author: Mathias Dahl <[EMAIL PROTECTED]> ;; This file is not part of GNU Emacs. ;; GNU Emacs is free software; you can redistribute it and/or modify ;; it under the terms of the GNU General Public License as published by ;; the Free Software Foundation; either version 2, or (at your option) ;; any later version. ;; GNU Emacs is distributed in the hope that it will be useful, ;; but WITHOUT ANY WARRANTY; without even the implied warranty of ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the ;; GNU General Public License for more details. ;; You should have received a copy of the GNU General Public License ;; along with GNU Emacs; see the file COPYING. If not, write to the ;; Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, ;; Boston, MA 02110-1301, USA. ;;; Commentary: ;; ;; file-props.el provides a way to "tag" or "label" your files. ;; Actually, the functionality is generic and supports adding any type ;; of property to your files. Right now "tags" and a "comment" can be ;; added. ;; ;; After having added this meta data you can use it to find files in ;; different ways. Provided is a command to mark all files having a ;; certain tag in a dired buffer. ;; ;;; Installation: ;; ;; Place this file in your `load-path'. ;; ;; Put this in your .emacs file: ;; ;; (require 'file-props) ;; ;; If you want to activate display of comment and tags for Dired, put ;; this in your .emacs as well: ;; ;; (file-props-dired-activate-display) ;; ;; If you want to disable the display temporarily, do M-x ;; file-props-dired-deactivate-display ;; ;; To setup convenient Dired keybindings, put this: ;; ;; (file-props-dired-setup-keybindings) ;; ;;; Usage: ;; ;; - Adding tags: ;; ;; In dired, mark a couple of files and type M-x ;; file-props-dired-add-tags RET. ;; ;; There are three versions of tag input, see option ;; `file-props-read-tag-multi-method' for more information. ;; ;; - Finding files: ;; ;; Type M-x file-props-find-tags-dired RET. ;; ;; Enter a tag and type RET. ;; ;; You will be presented with a dired buffer containing the files ;; having the tag you searched for. ;; ;; - Marking files: ;; ;; You can use the commad `file-props-dired-mark-from-tag' in a Dired ;; buffer to mark files that have a certain file tag. It is ;; equivalent to how some of the other `%-commands' in dired works. ;; ;; - Edit tags and comments: ;; ;; Mark some file in Dired, either manually or using ;; `file-props-dired-mark-from-tag', then execute `file-props-edit'. ;; This will open up a new buffer where you can edit tags can comments ;; easily. ;; ;; - Other uses: ;; ;; Currently, the only other command is `file-props-dired-add-comment' ;; which will add a comment property to the file. The idea is that ;; while tags are used to categorize or label your files, a comment is ;; more specific and can act as the description of the file. ;; ;; As explained above, tags and comments are just examples of meta ;; data you might want to add to your files, other types of data ;; should be easy to add if you want. Look at ;; `file-props-dired-add-tags' and `file-props-dired-add-comment' for ;; examples. ;; ;; ;;; Wish-list: ;; ;; - When searching for files with tags the user should be able to ;; specify multiple tags, not just one, when further tags are ;; specified (with completion) only those tags are offered which ;; have an intersection with the previous ones, (see del.icio.us) ;; ;; - Renaming and deleting tags. ;; ;; ;;; History: ;; ;; ;; Version 0.1, 2006-06-27 ;; ;; First release. ;; ;; Version 0.1.1, 2006-06-28 ;; ;; Removed warning when loading properties. It wasn't very ;; useful. ;; ;; Removed question about current directory from ;; `file-props-find-tags-dired'. I don't think this was needed ;; either. ;; ;; Replaced `read-string' with `completing-read' when reading tags to ;; search for. I know Drew will like this because it should enabled ;; `icicles' to assimilate this functionality... :) ;; ;; Added command `file-props-dired-mark-from-tag'. ;; ;; Added command `file-props-dired-edit'. ;; ;; Fixed problems with whitespace when splitting tags string entered ;; by the user. Two new functions was added, `file-props-trim-spaces' ;; and `file-props-split-and-trim'. ;; ;; Added a new way to enter multiple tags, using completion and made ;; this the default. The option ;; `file-props-read-tags-comma-separated' was added if the user wants ;; to use the old method, using a comma separated string. ;; ;; Version 0.1.2, 2006-11
Re: ;;; anything.el --- open anything
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes: Hi Tamas, >> That's nice, really nice. I'll have a lot of fun adding stuff to >> anything-config.el. > > BTW, don't you want to be in charge of anything-config.el? Yes, why not? I'll create a emacswiki page for anything.el tomorrow (if the weather is as bad as the news said). > It may be better if its development is coordinated rather than > everyone hacking away on it randomly. > > You seem to be suitable for the job if you're interested. ;) Sure, I am. Bye, Tassilo -- Most people fear the Reaper. Chuck Norris considers him "a promising Rookie". ___ gnu-emacs-sources mailing list gnu-emacs-sources@gnu.org http://lists.gnu.org/mailman/listinfo/gnu-emacs-sources
Re: ;;; anything.el --- open anything
On Jul 21, 8:27 pm, Tassilo Horn <[EMAIL PROTECTED]> wrote: > "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes: > > That's nice, really nice. I'll have a lot of fun adding stuff to > anything-config.el. BTW, don't you want to be in charge of anything-config.el? It may be better if its development is coordinated rather than everyone hacking away on it randomly. You seem to be suitable for the job if you're interested. ;) > Who needs Spotlight if he has emacs, right? ;-) Spotlight can be a backend for a source. :) ___ gnu-emacs-sources mailing list gnu-emacs-sources@gnu.org http://lists.gnu.org/mailman/listinfo/gnu-emacs-sources
Re: ;;; anything.el --- open anything
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes: Hi Tamas, [snip] > Now, how's THAT sound? ;) That's nice, really nice. I'll have a lot of fun adding stuff to anything-config.el. Who needs Spotlight if he has emacs, right? ;-) Best regards, Tassilo -- No person, no idea, and no religion deserves to be illegal to insult, not even the Church of Emacs. (Richard M. Stallman) ___ gnu-emacs-sources mailing list gnu-emacs-sources@gnu.org http://lists.gnu.org/mailman/listinfo/gnu-emacs-sources
Re: realplay.el interface with Real Player v. 1879
On Sat, 21 Jul 2007 00:51:59 -0400 Richard Stallman wrote: > > Does the mplayer site include a list of non-free codecs? Does it say > > where to get them? That would encourage people to install them. > > Yes. > > That's the problem I thought there was. > > These people have done a lot for your goals (maybe with the `wrong' > motives, but why care?). > > This isn't about their motives. This is about whether recommending > mplayer serves our goals or undermines them. Then please have a look at the *long* list of supported codecs by the free libavcodec. They did a lot for your goals. David ___ gnu-emacs-sources mailing list gnu-emacs-sources@gnu.org http://lists.gnu.org/mailman/listinfo/gnu-emacs-sources
Re: ;;; anything.el --- open anything
On Jul 20, 9:22 pm, Tassilo Horn <[EMAIL PROTECTED]> wrote: > > The problem with that no-vc-approach is, that users who extend > anything.el to fit their needs will have to redefine a bunch of > variables, e.g. > > (setq anything-sources '((...))) > (setq anything-type-actions '((...))) > > and so forth. Yep, and this is the recommended way. Any serious user of anything should radically redefine these and other variables. The provided defaults are not really practical, they are there only to show off anything features. For example, why should be completions from Complex Command History delayed? No real practical reason, I added the delay attribute only to test and demonstrate this feature. That's why I don't use the defaults either, and neither should others. People's needs are so different, that it's unlikely there could be sensible defaults which would appeal to most people. > If you now add a bugfix or little change to the original > definition, that won't propagate to the users. So I'd recommend to use a > distributed vc system nevertheless. Then any hackish user could use > their own branches and sync painlessly to incorporate the changes you > made. This is the hackish way and I'd rather like a clear separation between anything the platform and predefined anything configurations. Regardless of the version control issue. For that purpose, I created anything-config.el and moved the two existing predefined sources to it, and buffer actions as an example. Predefined anything configurations should be collected there, so that users can use those what they prefer. In addition to predefined sources and actions people can even publish alternative anything- source configurations there. I don't plan to touch anything.el itself in the future for changes in the default configuration, except if a new feature is added and it should be demonstrated with the example sources, but I don't expect it to happen very often. > To make anything.el better suited for extending it on the user side I'd > recommend to clean it up a bit, e.g. the example sources in > `anything-sources' should all be defined with `anything-source-FOO' > variables and the same for `anything-type-actions'. These should be added to anything-config.el instead. The configurations in anything.el are to show off features, they are examples. Their proper, practical versions should be maintained in anything-config.el. > Since you don't have "too much time" I volunteer to create a repository > for you and to make those little cleanups during this weekend. > > How does that sound? C'mon, that's a offer you cannot decline. :-) Unlike how it seems I do appreciate your offer. :) I prefer version control systems myself. The thing is I have used different operating systems and different computers while hacking on anything and the simplicity of emacs wiki was very convenient, because there was no need to set up additional tools, besides emacs. Here's what I think: I hereby authorize you and others to hack on anything-config.el uploaded to Emacs wiki. :) Add your command completion source, actions and stuff, and you can even put it under version control if you wish. It will change much more often than anything.el itself, I think. For the time being, anything.el should be left on Emacs Wiki. Let's see how it goes with anything-config.el first and if there is a need at all to put anything.el too under version control (no more ad-hoc changes in the default configuration). I expect most of the changes will be in the configurations and the base platform won't be touched that often. Now, how's THAT sound? ;) ___ gnu-emacs-sources mailing list gnu-emacs-sources@gnu.org http://lists.gnu.org/mailman/listinfo/gnu-emacs-sources
