Slyz is right; And yes, it's probably linux specific, since only it has separate 'selection' buffer.
All deeds are specified by one comma-delimited preference "dailyDeedsOptions". Order matters. Built-in deeds are simply called by referring to their built-in name; these are viewable by pulling up the Daily Deeds tab and looking in the "Built-in Deeds" list.
Custom Deeds
Custom deeds provide the user with a way of adding buttons or text to their daily deeds panel that is not natively provided for. All deeds start with the keyword $CUSTOM followed by a pipe (|) symbol. As you are constructing a custom deed, you separate the different arguments with pipes. All deed types except for Text require a preference to track. If you want to add a button that is always enabled, you will have to create a dummy preference that is always false. There are currently 5 different types of custom deeds. Remember that all of these "acceptable forms" are prefaced by $CUSTOM|. Command - execute a command with a button press acceptable forms: Command|displayText|preference Command|displayText|preference|command Command|displayText|preference|command|maxUses displayText - the text that will be displayed on the button preference - the preference to track. The button will be enabled when the preference is less than maxUses (default 1). command - the command to execute. If not specified, will default to displayText. maxUses - an arbitrary integer. Specifies a threshold to disable the button at. A counter in the form of <preference>/<maxUses> will be displayed to the right of the button. Item - this button will use fuzzy matching to find the name of the item specified. Will execute "use <itemName>" when clicked. Will only be visible when you possess one or more of the item. acceptable forms: Item|displayText|preference Item|displayText|preference|itemName Item|displayText|preference|itemName|maxUses itemName - the name of the item that will be used. If not specified, will default to displayText. Skill - cast a skill that is tracked by a boolean or int preference. Will execute "cast <skillName>" when clicked. Will not be visible if you don't know the skill. acceptable forms: Skill|displayText|preference Skill|displayText|preference|skillName Skill|displayText|preference|skillName|maxCasts skillName- the name of the skill that will be cast. If not specified, will default to displayText. Must be specified if maxCasts are specified. maxCasts - an arbitrary integer. Specifies a threshold to disable the button at. A counter in the form of <preference>/<maxCasts> will be displayed to the right of the button. Text acceptable forms: Text|pretty much anything. You can supply as many arguments as you want to a Text deed. Any argument that uniquely matches a preference will be replaced by that preference's value. If you want to use a comma in your text, immediately follow the comma with a pipe character so it will not be parsed as the end of the Text deed.
textPane.setSelectionStart( 0 );
textPane.setSelectionEnd( 0 ); // don't have scrollPane scrolled to the bottom when you open it
The JTextComponents being referred to here are enabled, or else you wouldn't be able to interact with them. What you might be thinking of is that they are not editable. They are certainly handled differently, a component that is not enabled won't fire certain events.
Does it happen with other frames? eg. open the inventory frame, click " - Fine Tuning" and paste. Does it paste the value of the list item?
Yes.