Editing Clipboard Commands

Jump to navigation Jump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 33: Line 33:
  
 
== *>text ==
 
== *>text ==
The *>text command is used to open text files.  The command needs to be followed by the name of a file that can be opened with your system editor ( the key parameter is paremeters.ex_editor see '''[[Configuration Files For Python]]''' )  You can have multiple *>text commands in your clipped content, only lines with *>text will be attempted, other lines will be ignored.  Files are not currently tested to see if they exist, non-existent files may trigger side effects in your editor.  The content returned to the clipboard is all the lines that were identified as *>text lines.  Junk after the file name will be interperted as part of the file name, so leave it out of your file, this goes for spaces as well ( but I probably will fix this.  As with *>url the first line of the copied text must contain a command.
+
The *>text command is used to open text files.  The command needs to be followed by the name of a file that can be opened with your system editor ( the key parameter is paremeters.ex_editor see '''[[Configuration Files For Python]]''' )   
 +
 
 +
The code for the command is mostly in cmd_processor.do_star_text_line
 +
 
  
There is a transform for adding *>text in front of lines of file names.
 
  
The code for the command is mostly in cmd_processor.do_star_text_line
 
  
 
== *>shell ==
 
== *>shell ==

Please note that all contributions to OpenCircuits may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see OpenCircuits:Copyrights for details). Do not submit copyrighted work without permission!

Cancel Editing help (opens in new window)