In a buffer~ that changes name multiple times, is there any way of outputting the current name of that buffer~?

outputting-current-buffer-name

On 15 nov. 08, at 17:22, Jay Bodley wrote:

> In a buffer~ that changes name multiple times, is there any way of 

> outputting the current name of that buffer~?

If you want to know the name of the file, you might want to have a 

> G'morning
>
> In a buffer~ that changes name multiple times, is there any way of  
> outputting the current name of that buffer~?

If you want to know the name of the file, you might want to have a  
look to the info~ object.

info~ does not output the buffer~ name, only the file name.

I'm writing an object that will need to know the buffer name of every patch that it's included in (or buffer~ that it's used for). I want to have the buffer name output to send to a [prepend symbol]-[set $1] to send to groove~. What I'm going for is something like the #1 argument for numbers.

info~ does not output the buffer~ name, only the file name.
I'm writing an object that will need to know the buffer name of every patch that it's included in (or buffer~ that it's used for).  I want to have the buffer name output to send to a [prepend symbol]-[set $1] to send to groove~.  What I'm going for is something like the #1 argument for numbers.


When you set the name of the buffer you could also store the name in zl reg or a central coll then you could query the name quite simply.

just put the name out, right after you changed it.

ok, but how about if the buffer name is given as an argument?

On 15 nov. 08, at 20:28, Jay Bodley wrote:

> ok, but how about if the buffer name is given as an argument?

well if you had the courage to write it as an argument, there's good 

chance that you could write it somewhere else too where you could 

query it, right? Otherwise, you can can make some abstraction which 

would do both (declaring the buffer, and storing its name).

well if you had the courage to write it as an argument, there's good  
chance that you could write it somewhere else too where you could  
query it, right? Otherwise, you can can make some abstraction which  
would do both (declaring the buffer, and storing its name).

outputting current buffer~ name