| Re: kscope?
Sep 2 2006 on Discussion |
In version 1.4.1, which I just tested, kscope does not provide a settings menu where you can configure the settings of the ktexteditor that is used. Thus, the emacsextensions plugin cannot be enabled.
Please file a bugreport to kscope. |
|  | | Re: FreeBSD
Jan 22 2006 on content noatun-normalize |
Hi,
could you please give me the list of instructions you performed for compiling?
In case you did:
./configure [--prefix=...]
make
make install
please try to create the configure file yourself by calling
make -f Makefile.cvs
in the top source directory. Then try the steps above again.
Hope that helps,
Felix |
| | | Re: emacs kill-line
Aug 5 2005 on content ktexteditor - emacsextensions |
For this to work I would have to find out what the last executed command was.
Unfortunately I couldn't find a way to do it. I tried using the undo count, but this is too fine grained and seems to also change when you move the cursor between two kill-region commands.
:-( |
| | | Re: emacs kill-line
Apr 12 2005 on content ktexteditor - emacsextensions |
Yes, it does. As of now I just ignored concatenating coalescent kill-regions in the kill-buffer.
But now that someone caught me ;-), I'll have a look how difficult it would be to mimic Emacs' behavior with respect to this. |
| | | Re: delete next character
Apr 5 2005 on content ktexteditor - emacsextensions |
Done :-)
The action will only be available in libkatepart versions < 3.4 since the katepart supports it in 3.4 itself. |
| |
| | | Re: Unable to use it
Apr 1 2005 on content noatun-normalize |
> I am using SuSE 9.2 Professional.
I could also provide an rpm package converted from the Debian package.
If you would be so kind as to test it, I could find out if this makes sense as I don't have access to a SuSE box. |
| | | Re: Unable to use it
Apr 1 2005 on content noatun-normalize |
> First a suggestion: Remove absolute
> path in line no.15 in
> gaineditorwidgetbase.cpp
Thanks for pointing this out, this is also in the gaineditorwidgetbase.ui from which the cpp file is generated. This must have slipped in when adding the separator widget from qt designer.
> How should your plugin be used? When
> I insert "NoatunNormalize" effect
> nothing usual happens and when I
> load your plugin it does not show
> any option.
The normalize effect should not be used directly as of now. When the plugin is loaded it activates the effect and feeds it with the correct gain adjustments automatically.
To check if your setup works, activate the plugin and play a song. Then do one of the following:
1. If it's an ogg vorbis file having a vorbisgain (replaygain) tag, just open the gaineditor and see if the gain adjustment value is shown correctly.
2. Otherwise wait a bit for normalize or vorbisgain to have computed the gain adjustment and open the gain editor then, the value should be displayed.
Change the value in the gain editor dialog to see if it works. The gain editor can be reached from the actions menu that is in the context menu of the noatun interface.
I hope this helps, don't hesitate to ask again. |
| | | Re: Re: Re: Re: Thanks!
Mar 15 2005 on content ktexteditor - emacsextensions |
I'm glad you worked it out.
Ctrl-K is not fully compatible to Emacs's kill-line yet when you call it at the end of a line. The new line character should be removed then. This will be fixed in the next release.
Regards,
Felix |
| | | Re: menu
Mar 13 2005 on content ktexteditor - emacsextensions |
Done.
I don't use it myself, but if it advertises the actions and their shortcuts better, it won't harm.
Felix |
| |
Search people
Current visitors
New users
Birthdays
Most active users
Back
|
|
