www.archive-org-2013.com » ORG » K » KATE-EDITOR

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".

    Archived pages: 354 . Archive date: 2013-10.

  • Title: Kate | Get an Edge in Editing | The Kate Editor Homepage
    Descriptive info: .. Kate | Get an Edge in Editing.. The Kate Editor Homepage.. Main menu.. Home.. Features.. Get It.. Get Help.. Join Us.. Featured Articles.. VI Mode.. The Team.. About.. KatePart.. Multiple Keyboard Layouts and Shortcuts.. by.. Dominik.. October 7, 2013.. 5 Comments.. KDE has a very handy feature to switch keyboard layouts on the fly.. This is for instance useful if you use the German keyboard layout by default, and the US layout for programming.. To enable keyboard layout switching, go into System Settings Input Devices (category Hardware) Keyboard item Layouts tab: Here,.. Read more.. Multi-Line Text Editing in Kate.. September 9, 2013.. 7 Comments.. Right after the vim blog and the what s new in 4.. 11 blog we have another feature that was long requested and finally is available in 4.. 12: Multi-line editing in block selection mode.. Needless to say that it also supports undo/redo and pasting text.. Kudos go to Andrey Matveyakin for implementing it!.. Kate in 4.. 11.. 3 Comments.. Another release cycle gone, and the KDE Software Compilation 4.. 11 is out in the open (well, for quite some time already), and with that it is time to talk about what changed in Kate the last half year since the 4.. 10 release..  ...   Building Blocks) allocator to overwrite malloc/free/* and want to use Valgrind for leak checking and fail, here is the simple trick to get it working: valgrind --soname-synonyms=somalloc=\*tbbmalloc\* your-application-here I missed that hint in the Valgrind documentation for my first tries Btw.. , the scalable allocator from.. Ramblings about compilers.. July 8, 2013.. In my job I work on binary and source level analysis software running on Linux and Windows.. One of my tasks is to maintain the build farm and compile environment, therefore I am responsible for keeping care of the compilers and libraries we use (like the beloved Qt, congratulations for the nice 5.. 1 release,.. Page navigation.. Page 1 of 55.. 1.. 2.. 3.. 55.. Search for:.. Recent Posts.. Recent Comments.. sinma.. on.. Using the Projects Plugin in Kate.. Wolf on.. Recent Commits.. Revision 02de38f7: Typo corrections, and making punctuation more consistent in lists and in a table.. Revision e553de3c: Revert This should finally fix the problem, that the first time the completio.. Revision e3d4bccf: Use base color for completion list background.. Revision a8907d69: Abbreviation matching: performance optimizations to prevent the worst case.. Revision 7ec700fe: Fix obvious typo in previous commit (sorry).. Meta.. Log in.. Entries.. RSS.. Comments.. WordPress.. org.. 2013.. All Rights Reserved.. Created using.. PressWork..

    Original link path: /
    Open archive

  • Title: Features | Kate | Get an Edge in Editing
    Descriptive info: Application Features.. window splitting (horizontal vertical).. multi-document interface (MDI).. plugin: embedded terminal, SQL plugin, build plugin, GDB plugin, Replace in Files, and more.. session support.. General Features.. encoding support (Unicode and lots of others).. bi-directional text rendering support.. line ending support (Windows, Unix, Mac), including auto detection.. network transparency (open remote files).. extensible through scripting.. Advanced Editor Features.. bookmarking system (also supported: break points etc.. ).. scroll bar marks.. line modification indicators.. line numbers..  ...   checking.. highlighting of selected words.. Programming Features.. scriptable auto indentation.. smart comment and uncomment handling.. auto completion with argument hints.. vi input mode.. rectangular block selection mode.. Search Replace.. incremental search, also known as find as you type.. support for multiline search replace.. regular expression support.. search replace in multiple opened files or files on disk.. Backup and Restore.. backups on save.. swap files to recover data on system crash.. undo / redo system..

    Original link path: /about-kate/
    Open archive

  • Title: Get It | Kate | Get an Edge in Editing
    Descriptive info: Distribution Packages.. As Kate and KWrite are part of the.. KDE project.. , you can get them simply by installing the KDE packages.. from your Linux distribution.. To get Kate for Mac OS X, please visit.. KDE s Mac pages.. Windows packages are available through the.. KDE on Windows.. project.. Building Kate from Sources.. This quick howto explains how to build Kate without touching your stable KDE installation.. Right now, Kate s source code is located on.. git.. kde.. To build Kate from git, you need KDE SC = 4.. 8.. Further,.. make sure you have the following packages installed:.. and the.. kdelibs development package.. (and CMake).. to install on openSUSE:.. sudo zypper install git libkde4-devel libkactivities-devel libqjson-devel python-kde4-devel.. to install on Ubuntu and derivates:.. sudo apt-get install g++ make git cmake kdelibs5-dev libqjson-dev python-kde4-dev python-qt4-dev.. to install on Arch Linux:.. pacman -S git automoc4 cmake kdebindings-python (installation with base-devel + kde).. to install on RHEL:.. yum install gcc-c++ kdelibs-devel kactivities-devel qjson-devel sip-devel PyKDE4-devel.. to install on Fedora:.. yum install gcc-c++ kdelibs-devel kactivities-devel qjson-devel sip-devel pykde4-devel.. create and change into a KDE development directory:.. mkdir -p ~/kde/usr; cd ~/kde.. get a copy of the Kate code:.. git clone git://anongit.. org/kate.. create and change into a build directory inside the kate directory for compilation:.. cd kate; mkdir build; cd build.. Use a run.. sh script as shown below to set the right environment variables, else make install might fail later.. run the configure process with cmake: (-DBUILD_KTEXTEDITOR=1 will install new ktexteditor interfaces from kate.. git, otherwise, you need  ...   script executable with.. chmod 755 ~/kde/run.. Now you can run the compiled Kate version with.. sh kate.. Just calling kate directly will start the system version of Kate.. Your copy of Kate contains all of the Kate code, i.. e.. : the KTextEditor interfaces, Kate Part, KWrite and the Kate Application.. You can keep your copy up-to-date by typing.. `git pull --rebase`.. in.. ~/kde/kate.. Feel free to send patches to our mailing list.. kwrite-devel@kde.. And join.. #kate.. irc.. :–).. Building the Kate Handbook.. The current stable version of the Kate Handbook is available on the.. KDE documentation webpage.. We very much welcome any updates to improve the Kate s documentation.. The source of the documentation is in the doc -subfolder.. To create the final html pages, switch to the doc -folder and first create a folder called html/kate and html/kwrite.. Here all the html ouput of the *.. docbook files will be generated.. Then use meinproc4 to generate the html ouput:.. mkdir -p html/kate mkdir -p html/kwrite # build Kate documentation cd html/kate meinproc4 --check.. /.. /kate/index.. docbook # or build KWrite documentation cd html/kwrite meinproc4 --check.. /kwrite/index.. docbook.. After a short moment the generation of the documentation will be finished.. Then point your web browser e.. g.. to ~/kde/kate/doc/html/kate/index.. html to view the result.. We are very happy for every patch!.. Building the API Documentation.. Creating the API documentation for the KTextEditor interfaces works by entering the following commands:.. cd kate/ktexteditor /path/to/kdelibs/doc/api/doxygen.. sh --recurse \ --doxdatadir=/path/to/kdelibs/doc/common.. The API documentation is then generated into the subfolder kate/ktexteditor/ktexteditor-apidocs..

    Original link path: /get-it/
    Open archive
  •  

  • Title: Get Help | Kate | Get an Edge in Editing
    Descriptive info: Before looking for support, be sure to read the available documentation, whether that is the.. application handbook.. , developer documentation or other documentation.. Also read the information pages about.. Kate.. ,.. KWrite.. and.. Kate Part.. Get in touch.. When in need for help, you have the following options to get in touch with Kate developers and users:.. Use our mailing list,.. The mailing list is open, that is you do not need to be subscribed to contact us.. Do not forget to ask to be CC d in answers in that case.. To subscribe, visit the.. kwrite-devel mailing list.. For archives, go.. here.. Mark Mail has a.. great overview.. of our list, too.. Visit our IRC channel.. #kate at irc.. You can often meet Kate developers there, and  ...   mailing lists, IRC channels and web forums.. If you have a problem with one of these applications and you are not sure if this is a bug of the Kate Part then please first report it to them.. Please prefer these public channels over contacting the authors in private.. Using the KDE bug system.. The KDE bug tracking system at.. http://bugs.. is used for managing all bugs related to Kate.. You can use the.. Help- Report Bug.. menu item found in most KDE applications to report bugs or wishes.. It will start the bug report wizard and fill in some information for you.. Be sure to include as much information as possible when reporting bugs, the better the report the better the chances we can fix the reported problem..

    Original link path: /support/
    Open archive

  • Title: Join Us | Kate | Get an Edge in Editing
    Descriptive info: How to help with Kate development.. If you want to help us develop Kate, KWrite or KatePart, you should.. join our mailing list.. Contacting us at.. #kate on irc.. is also a good idea, we are always happy to help you get started.. How to Build Kate.. Right now, you can build Kate very easily provided you use at least KDE 4.. 6.. Click here for a quick howto.. We are always happy about patches, just send them to our.. mailing list.. !.. Areas of work.. The main work area is the programming, but if you are not a programmer you can help in many other areas:.. Write and maintain documentation.. Write and maintain syntax highlight files.. Write and maintain scripts.. Maintain bug reports.. Provide us with useful feedback.. Help us by helping.. KDE.. As a part of KDE, Kate benefits from the KDE as a whole, apart from the excellent integration provided by KDE the help from the.. KDE translation team.. is invaluable.. C/C++ Coding Standards..  ...   { baz(); } }.. Kate s own C style indenter works nice for the code style we use in Kate code surprise.. Coding Standards for Python Plugins.. Besides delimiting blocks with 4 spaces, we do not have very strict rules for coding new Python plugins, basically having this kate variable line in your source files will do:.. # kate: space-indent on; indent-width: 4; mixed-indent off;.. In addition, most of us follow the PEP-8 style guide wherever appropriate.. Who codes desides.. If you are changing an existing plugin that follows the PEP-8 rules, please follow too.. Documenting your code.. We use Doxygen syntax to document code, and it s nice to document everything, even private code, since other people than you might get to work on it or just try to understand it.. For comments inside of functions, C++ single-line comments are preferred over.. multi-line C comments.. Good starting points.. Good ideas what to look at first are:.. Our bugs.. in the KDE bugtracker.. Our wishes.. Krazy issues..

    Original link path: /join-us/
    Open archive

  • Title: Featured Articles | Kate | Get an Edge in Editing
    Descriptive info: About the Kate Project.. Some information about the scope and aims of this project and the components that are created:.. Introduction to the Kate Project.. More Details on.. Kate / KWrite.. Getting Support.. People behind the project.. Using Kate and KWrite.. Information for the advanced user, how to use scripts, write extensions,.. Writing Syntax Highlighting Files.. Using Kate Modelines (document variables).. Configuring Kate with a.. kateconfig file.. Extending Kate with Scripts.. The Kate Vi Mode.. Using Kate Plugins.. Information about Kate plugins, which are cool?.. Terminal and FileBrowser (todo, any volunteers?)..  ...   Plugin (todo, any volunteers?).. Getting Involved.. Entry points for people wanting to contribute:.. Building Kate.. Debugging Kate with Qt Creator.. Writing KTextEditor Plugins.. Writing Kate Plugins.. Kate Bug Tracker.. Where to find our current issues? Help welcome to fix them.. Weekly Summary for Kate/KWrite Bugs.. Bug Charts.. Kate and KWrite Bug Tracker.. Feature Wishlist for Kate and KWrite.. Submit and Review Patches.. Kate Internals.. Concepts of the Kate implementation:.. The Text Buffer.. The Undo/Redo System.. More Kate Resources.. Build bot and co.. :.. build.. org Jenkins for kate.. git master.. Git Statistics..

    Original link path: /featured-articles/
    Open archive

  • Title: VI Mode | Kate | Get an Edge in Editing
    Descriptive info: Introduction.. Kate s VI mode is a project to bring Vim-like, modal editing to the.. Kate text editor.. and by extension to other KDE programs who share the same editor component.. The project started as a Google Summer of Code project in 2008 – where all the basic functionality was written.. I have continued to maintain and further develop this code and the number of missing features from Vim are slowly decreasing.. Most Vim users will already be productive in Kate s VI mode.. A list of what s missing is found at the bottom of the page.. This page is meant to be an updated overview of this work.. To enable the VI input mode, go to.. Settings → Configure Kate… → Editing → VI Input Mode.. It can also be toggled with the “VI Input Mode” setting in the “Edit” menu.. (The default shortcut key is Meta+Ctrl+V – where Meta usually is the Windows key).. Goals.. The goal of the VI mode is.. not.. to be a complete replacement for Vim and support.. all.. Vim s features.. Its aim is to make the “Vim way” of text editing – and the Vim habits learned – available for programs using the Kate text editor as their internal editor.. These programs include.. The Kate Text editor.. KWrite – KDE s simple text editor.. KDevelop – An advanced IDE for many programming languages.. Kile – A LaTeX editor.. The VI mode aims integrate nicely with the programs and deviate from Vim s behaviour where it makes sense.. For example,.. :w.. will open a save dialogue in Kate s VI mode.. Incompatibilities with Vim.. There are only a few features of Kate s VI mode which are incompatible with Vim (not counting things missing).. They are listed below together with the respective reasons.. Kate:.. U and ctrl+r is redo.. Vim:.. ctrl+r is normal redo, U is used to undo all latest changes on one line.. The reason for having U act as redo in Kate s VI mode is that the shortcut ctrl+r by default is taken by Kate s replace function (search and replace).. By default, the VI mode won t override Kate s shortcuts (this can be configured in Settings → Configure Kate… → Editing → Vi Input Mode), therefore a redo-action needs to be available as a “regular” key press, too.. Besides, the behaviour of the U command in Vim doesn t map well to Kate s internal undo system, so it would be non-trivial to support anyway.. :print shows the print dialogue.. :print prints the lines of the given range like its grandfather ed.. Commands like :print are available not only in the VI mode but for users using “regular” Kate, too – I have therefore chosen to let the :print command open the print dialogue – following the principle of least surprise instead of mimicking Vim s behaviour.. Y yanks to end of line.. Y yanks whole line, just like yy.. VI s behaviour for the Y command is in practice a bug; For both change and delete commands, cc /'dd will do its action on the current line and C /'D will work from the cursor column to the end of the line.. However, both yy and Y yanks the current line.. In Kate s VI Mode Y will yank to the end of the line.. This is described as “more logical”.. in the Vim documentation.. :map alters the selected lines of the document using the provided Javascript expression.. :map adds the provided mapping to Normal and Visual modes.. The map command was already reserved by Kate; in 4.. 12+, you can use a combination of :nmap and :vmap to replace it.. Supported Commands.. Supported normal/visual mode commands.. a.. Enter Insert Mode and append.. A.. Enter Insert Mode and append to EOL.. i.. Enter Insert Mode.. I.. Insert before first non-blank char in line.. v.. Enter Visual Mode.. V.. Enter Visual Line Mode.. c-v.. Enter Visual Block Mode.. gv.. Re-select Visual.. o.. Open new line under.. O.. Open new line over.. J.. Join lines.. c.. Change.. C.. Change to EOL.. cc.. Change line.. s.. Substitute char.. S.. Substitute line.. dd.. Delete line.. d.. Delete.. D.. Delete to EOL.. x.. Delete char.. X.. Delete char backward.. gu.. Make lowercase.. guu.. Make lowercase line.. gU.. Make uppercase.. gUU.. Make uppercase line.. y.. Yank.. yy.. Yank line.. Y.. Yank to EOL.. p.. Paste.. P.. Paste before.. r.. Replace character.. R.. Enter replace mode.. :.. Switch to command line.. /.. Search.. u.. Undo.. c-r.. Redo.. U.. m.. Set mark.. Indent line.. Unindent line.. Indent lines.. Unindent lines.. c-f.. Scroll page down.. pagedown.. c-b.. Scroll page up.. pageup.. c-u.. Scroll half page up.. c-d.. Scroll half page down.. zz.. Centre view on cursor.. ga.. Print character code.. Repeat last change.. ==.. Align line.. =.. Align lines.. ~.. Change case.. c-a.. Add to number.. c-x.. Subtract from number.. c-o.. Go to prev jump.. c-i.. Go to next jump.. c-w h.. Switch to left view.. c-w c-h.. c-w left.. c-w j.. Switch to down view.. c-w c-j.. c-w down.. c-w k.. Switch to up view.. c-w c-k.. c-w up.. c-w l.. Switch to right view.. c-w c-l.. c-w right.. c-w w.. Switch to next view.. c-w c-w.. c-w s.. Split horizontally.. c-w S.. c-w c-s.. c-w v.. Split vertically.. c-w c-v.. gt.. Switch to next tab.. gT.. Switch to prev tab.. gqq.. Format line.. gq.. Format lines.. q.. / q.. Begin/ finish recording macro using the named macro register.. Supported motions.. h.. Left.. left.. backspace.. j.. Down.. down.. enter..  ...   setting the hidden config option Vi Input Mode Emulate Command Bar to true.. in your katerc/ kwriterc/ kdeveloprc.. Missing Features.. As stated earlier, the goal of Kate s VI Mode is not to support 100% of Vim s features, however, there are some features which are sorely missed.. Visual block mode – especially the ability to prepend/append text to the visual block selection.. Having ex commands available in other programs than the Kate application.. The search code needs improvement and the * and # commands should just be regular searches.. If you miss other features or want to help on the ones mentioned above, feel free to contact me or send patches!.. Change Log.. 2010-05-16:.. Initial version.. Collected the information from blog entries and README files to make a single source of current information.. 2010-05-17:.. Ctrl.. +.. A and Ctrl+X added (increment/decrement number under cursor).. 2010-08-30:.. Moved page to kate-editor.. 2010-09-10:.. Fixed the text on the comma text object and made some formatting fixe.. s.. 24 Responses to.. François.. September 1, 2010 at 21:32.. Hi,.. I would like to read your source code.. Where can I find it? I didn t find anything in kate svn.. Thank you.. Regards.. Reply.. Erlend Hamberg.. September 1, 2010 at 23:39.. The source code for the vi mode is in kdelibs/kate/vimode.. September 9, 2013 at 13:08.. The source code has since moved, and can now be found at:.. https://projects.. org/projects/kde/applications/kate/repository/revisions/master/show/part/vimode.. Yaroslav.. November 6, 2010 at 18:39.. d% works really wrong.. November 7, 2010 at 13:42.. please report bugs at bugs.. org where it s possible to follow them up.. uu.. July 16, 2011 at 03:43.. “make mouse dragging start visual mode” ——when could this complete?.. Vi mode selection is not consistent with kate s cursor selection,this cause many trouble.. Svyatoslav Kuzmich.. July 25, 2011 at 16:45.. It s already implemented.. You can find it in the git version of Kate and help to test it.. July 26, 2011 at 19:09.. Thanks very much.. I ll test it right now.. Gary Kline.. October 3, 2011 at 20:44.. The _one_ vi feature that kate that I would like to see added is the abbreviations.. :ab i I or :ab tht that.. I am working on a text-to-speech application for people who are mute or speech-impaired and who cannot type very fast.. I have discovered that by having a standard list of roughly 130 abbrevs, typing ordinary English text can be speeded up by about 31%.. I have been a programmer for many years and am willing to add this feature or at least help with it.. Please let me know.. gary kline.. 李大双.. October 27, 2011 at 09:03.. 很不错的功能。支持.. January 27, 2012 at 14:46.. @李大双: 谢谢!:-).. alphi.. January 27, 2012 at 00:49.. What about remaping keys (using :remap.. for example when using a keyboard like colemak or bepo ?).. What is the best way to redo it (in vim I have my :remap commands in my vimrc).. January 27, 2012 at 11:46.. @alphi: There is experimental support for :nn[oremap] (normal mode remappings) for the Vi Mode.. These are saved in ~/.. kde/share/config/katerc.. It should be possible to write a short script to convert from Vim s format to the format used in the katerc file for normal mode mappings.. January 27, 2012 at 14:39.. Thx, it s working, in fact I was using fake vim from qtcreator, but it seems to be different to kate (I didn t manage to do the same key mapping as in kate).. But thx.. January 27, 2012 at 14:42.. @alphi: Ah.. Ok.. Ironically Qt Creator s “fake vim” does not support many (or any at all?) vim functionality, but just Vi functions, while Kate s “Vi mode” support a lot of Vim functionality like text objects (I could never live without them!).. Marcus.. June 25, 2012 at 04:05.. I am experimenting with Kate s Vi Mode, but I was stuck after my first :split! I could not close the split windows! In Vim, that would be a simple :q, but Kate closes __files__ (buffers?) with :q, not split windows.. So what s the command for closing split windows? I have tried :q, :close, C-w c, and right-clicking everywhere.. Artem.. September 27, 2012 at 21:12.. This page is in need of an update after Vegard Øye s great improvements to the VI mode.. vik.. October 27, 2012 at 20:38.. ywp doesn t insert the yanked word correctly (cursor should be at the end).. RobertK.. November 20, 2012 at 21:08.. How cool is that feature? Love it!.. Rob.. Federico Silva (@fedesilvaponte).. December 3, 2012 at 08:15.. Can I implement some mappings like imap jj.. This would be great, because I can t get used to press Esc everytime I want ot exit Insert Mode.. December 3, 2012 at 14:48.. Not yet, no.. Patches are welcome, though!.. You can use Ctrl-[ (or even Ctrl-C) or instead of Esc.. sybl.. January 3, 2013 at 03:37.. Is there any place to go to contribute in development or something? I m interested in helping improve the VI mode.. January 3, 2013 at 03:39.. Duh! Nevermind, I ve just found the primary tab saying Join Us.. Dayton_b.. January 11, 2013 at 20:45.. Sorry, I don t really have the programming experience (yet) to contribute, but can we get *zt* for make current line the top line and *zb* for make the current line the bottom line? It doesn t seem like this is the right place to make feature requests, but I don t know where to properly make the request.. Cancel Reply..

    Original link path: /kate-vi-mode/
    Open archive

  • Title: The Team | Kate | Get an Edge in Editing
    Descriptive info: These are the people who are or have been working on creating Kate, KWrite and KatePart.. If you are not mentioned and feel you should be — or is mentioned and feel you should not be,.. contact us.. Contact:.. cullmann@kde.. (Jabber: cullmann@jabber.. org).. Website:.. http://cullmann.. io.. Christoph started the application that later became Kate back in 2000, and have stayed with it as a core developer and active maintainer ever since.. He has contributed major parts of the code, and is the brain behind the excellent named sessions feature found in Kate 2.. 5.. Dominik Haumann.. dhaumann@kde.. http://www.. kate-editor.. Dominik joined the Kate Project back in early 2004.. Since then he constantly contributes e.. by maintaining the syntax highlighting files, reviewing patches and developing core features such as scripting support or the line modification system in Kate Part.. Joseph Wenninger.. jowenn@kde.. jowenn.. at.. Jowenn has been with Kate development since the early days, and is the developer behind Kate’s excellent syntax highlighting engine, the code folding system, the insertion template system and much more.. Milian Wolff.. mail@milianw.. de.. http://milianw.. Milian joined the Kate developers in 2009.. Since then, he actively contributes in many areas such as maintaining syntax highlighting files, fixing indentation scripts and writing unit tests.. He also likes to increase performance and fix general bugs he encounters while using KatePart in KDevelop.. ehamberg@gmail.. com.. http://hamberg.. no/erlend.. Erlend joined  ...   numbered text/lists, tables, Word/Excel/Powerpoint filters), KDE libs (common search/replace dialogs, timezone support), Kate (Python plugin support, and some plugins), KDEPIM (timezones, MAPI-based calendar, contact and mail readers), multi-language support with a Bengali focus (kxkb, Viki virtual keyboard.. ) as well as bits and pieces elsewhere in the Open Source world.. Gerald Senarclens de Grancy.. oss@senarclens.. eu.. http://find-santa.. Gerald uses Kate, Kile and KDevelop on a daily basis.. He mainly does QA and scripting to further improve the Kate editor component.. Pablo Martín.. goinnn@gmail.. https://github.. com/goinnn.. Pablo is a Django developer and uses Kate to code.. He joined the Kate Project in 2013, but since 2009 he has been developing plugins for Kate.. In 2011, he created a repository on github to develop these plugins and share them, now he codes them in the official repository.. Bernhard Beschow.. bbeschow@cs.. tu-berlin.. Bernhard joined the Kate Project in 2008 and is doing a great job in refactoring code in Kate to make it very easy to understand.. For instance, he is maintaining the excellent search replace feature as well as the undo/redo system.. Anders Lund.. anders@alweb.. dk.. alweb.. dk/.. Anders has been active in Kate development since the start back in 2000, and have contributed among others the view splitting mechanism (Kate), the External Tools feature (Kate), the document list color shading (Kate) and printing functionality (KatePart).. Hamish Rodda.. Michael Bartl.. Jochen Wilhelmy..

    Original link path: /the-team/
    Open archive

  • Title: About | Kate | Get an Edge in Editing
    Descriptive info: The Kate project develops two main products:.. , the advanced editor component which is used in numerous KDE applications requiring a text editing component, and.. , a MDI text editor application.. In addition, we provide KWrite, a simple SDI editor shell which allows the user to select his/her favourite editor component.. Kate is a multi-document editor part of KDE since release 2.. 2.. Being a KDE application, Kate ships with network transparency, as well as integration with the outstanding features of KDE.. Choose it for viewing HTML sources from konqueror, editing configuration files, writing new applications or any other text editing task.. You still need just one running instance of Kate.. With a multi-view editor like Kate you get a lot of advantages.. You can view several instances of the same document and all instances are synchronized.. Or you can view more files at the same time for easy reference or simultaneous editing.. KWrite is a simple text editor application, allowing you to edit one file at the time per window.. As Kate, KWrite uses the editor component..  ...   the article.. A Bit of History.. The Kate project started in December 2000 at sourceforge.. net.. In the first month Kate was known as KCEdit , with C standing for Cullmann, the last name of the author.. Over the time other people joined the project, so that the name was changed from KCEdit to Kant.. This name was motivated by the philosopher.. Immanuel Kant.. and was supposed to be more neutral and distinct compared to KEdit.. Time went on and Kant got more and more popular with new developers joining the project.. At that time Kant was officially included in the kdebase module of the KDE desktop as addon for the old KWrite application, which was quite a success.. Now all KDE users had access to our beloved text editor! the only big problem then was that the pronunciation of Kant sounds misleading in the English language for some people.. This was the reason why the name had to be changed again and the final name was.. (KDE advanced text editor).. You can read.. the full story here..

    Original link path: /about/
    Open archive

  • Title: KatePart | Kate | Get an Edge in Editing
    Descriptive info: KatePart is a fast and feature-rich text editor component with many advanced features.. It implements the KTextEditor interfaces, a common interface collection for text editor components in KDE, allowing it to be selected as the editor in applications that lets the user chose from different implementations, and it can use KTextEditor plug-ins.. KatePart is originally based on code from the KDE 1 richtext editor widget, but has been almost completely rewritten over the years.. It is the default text editor widget in.. Kate and KWrite.. and also the default to display text in.. Konqueror.. A lot of other applications use it as text editing component, too, like.. KDevelop.. Features include.. Syntax highlighting for more than 180 text formats, including popular programming languages like C/C++, Java, Ruby as well as markup such as HTML and XML.. Code completion interface that allows applications to provide text completion  ...   text.. Other mark types available for applications, for example for breadpoints or similar.. Support for UNIX, Windows and Mac.. EOL.. styles.. Advanced automatic bracket completion.. Marks, line numbers and folding regions display in margin.. Built-in command line, which can be extended by plugins.. Configurable per document by variables (modelines) embedded in the document text.. Configurable per mimetype or mimetype group by user defined file modes.. Configurable shortcut scheme for the editor widget.. Spell checking of full or partial content.. Encoding support.. Encoding conversion.. Plug-in support through KTextEditor.. Export of highlighted text to HTML.. Printing with support for syntax highlighting, line numbers and configurable header/footer.. KatePart is developed under a Open Source license to keep it available to the public and usable for other Open Source projects.. It is part of the.. kdelibs.. maintained by the.. KDE Project.. since KDE 3.. 0 and is released under the..

    Original link path: /about-katepart/
    Open archive

  • Title: Multiple Keyboard Layouts and Shortcuts | Kate | Get an Edge in Editing
    Descriptive info: Common.. Users.. To enable keyboard layout switching, go into System Settings Input Devices (category Hardware) Keyboard item Layouts tab:.. Here,.. [x] Configure layouts.. is checked, enabling the list view.. I added the German keyboard layout, and then the English (US) layout.. Notice also, that the shortcut is set to.. Ctrl+Alt+K.. Clicking apply, a tiny little indicator appears in the panel:.. You now can quickly switch with Ctrl+Alt+K between the German and the US layout.. Quite efficient, especially since the keyboard layout config page allows to switch the language on application basis.. Unchanged Keyboard Shortcuts.. Switching the keyboard layout has one potential issue, though: The shortcuts remain unchanged.. So if undo is mapped to.. Ctrl+z.. in the German layout, it is still mapped to.. in the US layout.. Note that by z we refer to the hardware key on the keyboard.. As a consequence, in the US layout, hitting the hardware key y on the German keyboard inserts the character z , but the z in.. is still on the hardware key z.. This behavior may or may not be wanted.. Getting more into detail reveals that the order of the keyboard layouts in the first screen shot is of importance: If you first add the German.. de.. layout, and then the English.. us.. layout, then the shortcuts will always use the Germany keyboard layout, independent of what keyboard layout is chosen.. Reversely, if you first add the English us layout, and then the German.. layout, then the shortcuts will always use the English.. keyboard layout.. So it seems that the order defines a priority, and the shortcuts always use the first entry in the list.. The correct solution to fix this would (in my humble opinion) be to add an option.. [x] Shorcuts follow keyboard layout.. or similar.. But since this option does not exist, let s do a quick hack to still get what we want here.. A Workaround.. First we reset the shortcut in the settings of the keyboard layout options:.. Click apply and close the dialog.. Now, the shortcut.. is unbound.. Our idea is now to create a script that toggles the keyboard layout by calling.. setxkbmap.. with the appropriate parameters and bind this script via a global shortcut to.. To this end, we first have to create the script.. So let s first type `.. setxkbmap -query.. ` in the console and check the output.. For me, this results in:.. $ setxkbmap -query rules: evdev model: pc101 layout: de,us variant: nodeadkeys,.. From this, we can follow that the current xkb layout is achieved with:.. setxkbmap -model pc101 -layout de,us -variant nodeadkeys.. Now, let s switch the.. de,us.. to.. us,de.. and try the following:.. setxkbmap -model pc101 -layout us,de -variant nodeadkeys.. Notice, that the keyboard layout indicator in the panel switched to.. Calling the first variant with.. again, we get back to the German layout.. This discovery leads us to the following script.. switch-keyboard-layout.. #!/bin/sh # query xkb map: us,de - us is primary; de,us - de is primary dummy=`setxkbmap -query |  ...   : This issue was reported as KDE.. bug #197552.. in 2009, and resolved as an upstream issue.. However, it never was reported to Qt upstream.. If I may say so, this is not how resolving bugs in KDE usually works.. Grrr.. Tags:.. planet.. About.. Dominik is a PhD student at the Control Theory and Robotics Lab, TU Darmstadt, as part of the.. Research Training Group GKMM (GRK1362).. My research focuses on.. state estimation in distributed systems.. As hobby, I contribute to the KDE project and work on the Kate application and editor component.. 5 Responses to.. Andriy Rysin.. October 7, 2013 at 23:07.. https://bugreports.. qt-project.. org/browse/QTBUG-32908.. October 8, 2013 at 11:14.. I’m pretty sure this is not the real issue.. According to the qt bug report above, this issue was fixed prior to Qt 4.. I’ve tested Qt 4.. 1 it’s not fixed.. It’s neither fixed in Qt 4.. 5, and I also checked out the Qt 4.. 8 branch which includes a revert of the respective commit that is supposed to lead to this issue: And even with the newest 4.. 8 branch it doesn’t work.. So no, this is certainly not fixed, sorry.. Wolf.. October 8, 2013 at 01:51.. Hi Dominik,.. I m doing the same German layout for writing German texts, US layout for programming and the shell.. I m using caps lock to switch layouts.. Concerning shortcuts: honestly, I don t know if I need to type Ctrl-y or Ctrl-z to undo.. Most of the time I probably try one or the other shortcut.. While I have no problem with braces, brackets, and slashes, y/z gives me a constant headache.. On the other hand, when writing English, I expect the z to be left of x, while when writing German, I expect it to be right of t.. Strange, isn t it? So far, there seems to be no good alternative.. October 8, 2013 at 11:16.. I can see the advantage of having fixed shortcuts all the time.. But let s face it: Say you want to change the keyboard shortcuts for a guest who is accustomed to another keyboard layout, you are doomed.. No easy way around it.. This is certainly a bug, not a feature.. Really.. It s just inconsistent.. October 18, 2013 at 22:09.. The problem is that the shortcuts change in GTK apps (which counts LibreOffice, Firefox and Thunderbird, Pidgin, Gimp, etc) while they doesn’t change in Qt apps and SDL games.. That’s really sad because it’s really practical to use an ergonomic keyboard layout (Dvorak, Colemak, Bépo, Neo…) but keeping qwerty or azerty shortcuts.. Damn GTK.. I don’t understand why some people use their local layout and US qwerty for programming.. For example, French azerty or German qwertz are almost as efficient, if not more than qwerty for programming.. If you really want to have a good programming layout, you can use programmer Dvorak, Neo (for German) or Bépo (for French).. Colemak isn’t good for programming because it has the same characters position than US qwerty..

    Original link path: /2013/10/07/multiple-keyboard-layouts-and-shortcuts/
    Open archive



  •  


    Archived pages: 354